# gateway A gateway is an intermediate system connecting two or more computer networks and enabling communication between them; in Internet documentation, it is an IP-level router. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## TypeSafe AI's Jev now available on AI Gateway DevFeed: [TypeSafe AI's Jev now available on AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [gateway](), [SDKs](), [API](), [Software]() Tags: [ai-gateway](), [api](), [evaluation](), [gateway](), [model](), [queue](), [retry](), [sdk](), [software](), [support](), [typesafe-ai]() ### AI overview Vercel's AI Gateway now supports TypeSafe AI's Jev, a probabilistic decision model that returns typed Choice, Score, and Boolean answers with probabilities. The changelog describes parallel evaluation, AI SDK 7 integration through an experimental evaluate API, example routing and review workflows, and provider options including Zero Data Retention and No Training. ### Source excerpt Jev from TypeSafe AI is now available on AI Gateway. Jev is a probabilistic decision model for software: state goes in, typed Choice, Score, and Boolean answers come out. Regular language models generate text one token at a time, which the application then parses and validates. Jev evaluates all declared questions in parallel and returns typed answers plus probabilities directly. That removes unnecessary text generation and makes it straightforward to automate clear cases while routing uncertain ones to review. TypeSafe reports Jev was up to 193.6x faster and 444.6x cheaper than LLMs on its workflow evaluations. Example use cases include: Choosing the next tool or subagent in an agent loop Deciding whether to continue, retry, ask the user, or stop Scoring urgency or risk before an action Verifying model outputs and enforcing guardrails. AI SDK 7 exposes Jev through the experimental evaluate API. Choice selects an option, Score grades an ordered rubric, and Boolean estimates the probability of true. Install the current AI SDK (AI SDK 7.0.105 onwards supports the evaluate API): Each evaluation specifies: model: the evaluation model to call, state: the shared string, object, or array to evaluate, and questions: a map of named decisions to make about that state. Call the model with typesafe-ai/jev. This example turns one support case into a queue, priority, and refund-review decision, with uncertain routing sent for manual review: The result preserves question IDs and Choice keys. TypeSafe reports separate Choice and Score confidence in result.providerMetadata.typesafe.confidence. Calibrate probabilities and confidence against labeled examples from your workflow. Jev supports Zero Data Retention and No Training, enabled per request in the example. Evaluation calls also appear in logs and custom reporting, count toward budgets, and accept other Gateway provider options in the same providerOptions.gateway object. Read the documentation on evaluation models on AI Gateway f ## Google tag gateway: Now on Webflow DevFeed: [Google tag gateway: Now on Webflow]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Webflow Blog]() Topics: [gateway](), [webflow](), [Google](), [Confidential Computing](), [data](), [configuration](), [Deployment]() Tags: [confidential-computing](), [configuration](), [conversion](), [data](), [deployment](), [development](), [gateway](), [google](), [measurement](), [webflow]() ### AI overview Webflow announces Google tag gateway, which routes conversion data through a site's first-party infrastructure. Existing native Google tag integration users can activate it by republishing their site, while new users can follow a code-free setup workflow. ### Source excerpt When you build on Webflow, you're creating experiences designed to help your business stand out and grow. Underpinning those experiences with a strong measurement foundation can help you understand what's driving results and make more informed marketing decisions. Now, Webflow makes it easier to strengthen your measurement foundation. ## IPFS is moving beyond the sponsored gateways DevFeed: [IPFS is moving beyond the sponsored gateways]() Original publisher: [Read original article]() Published: 2026-08-25T00:00:00Z Content type: release Language: en Sources: [IPFS]() Topics: [IPFS](), [gateway](), [P2P](), [browser]() Tags: [distributed](), [gateway](), [ipfs](), [object-object](), [open-web](), [self-hosted](), [time]() ### AI overview IPFS is changing how the ipfs.io and dweb.link gateways operate, shifting content retrieval from centralized servers toward service workers that connect directly to peers and verify content in the browser. The article also describes self-hosted gateways, browser-based IPFS nodes, and paid pinning and retrieval providers as alternatives. ### Source excerpt How IPFS is shifting from centralized public gateways to distributed infrastructure and client-side retrieval. ## 【Istio 控制面】选型收束与开放问题：CRD、Gateway API 与 eBPF L4 的排除树 DevFeed: [【Istio 控制面】选型收束与开放问题：CRD、Gateway API 与 eBPF L4 的排除树]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-11T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [istio](), [gateway](), [eBPF]() Tags: [ambient](), [cilium](), [ebpf](), [experimental](), [gamma](), [gateway](), [gateway-api](), [istio](), [kubernetes](), [mesh](), [network](), [open-problems](), [selection](), [xds]() ### AI overview The concluding article in an Istio control-plane series presents a mechanism-based decision tree for choosing among Istio CRDs, Gateway API/GAMMA, and eBPF L4 networking. It explains that Istio CRDs and Gateway API are alternative configuration inputs compiled by istiod into xDS resources, while eBPF L4 avoids xDS entirely. It also identifies open questions around configuration-activation SLOs, Ambient maturity, and coexistence between configuration models. ### Source excerpt 用机制排除树收束 Istio CRD 翻译、Gateway API/GAMMA 与 eBPF L4 的选型边界，回收系列阅读路径，并列出推送 SLO、Ambient 成熟度、GAMMA 双轨等开放问题；不做延迟排行榜。 ## Progressive Delivery with Argo Rollouts, Isovalent and Gateway API DevFeed: [Progressive Delivery with Argo Rollouts, Isovalent and Gateway API]() Original publisher: [Read original article]() Author: Christian Hernandez Published: 2026-08-06T07:01:00Z Content type: tutorial Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [progressive delivery](), [Argo Rollouts](), [gateway]() Tags: [argo-rollouts](), [delivery](), [gateway](), [progressive-delivery]() ### AI overview This article explains how progressive delivery controls traffic to newly deployed Pods, focusing on header-based canary deployments with Argo Rollouts and Gateway API. ### Source excerpt Progressive delivery is not only about creating the new Pods, it is also about controlling which traffic reaches them. This blog explores Header-based canaries with Argo Rollouts and Gateway API ## Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes DevFeed: [Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-24T16:28:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [networking](), [Routing (disambiguation)](), [Internet](), [gateway](), [Networks]() Tags: [bgp](), [cpu](), [flexibility](), [internet-architecture](), [isp](), [memory](), [network-engineering](), [network-operations](), [route](), [router](), [routing](), [routing-policy](), [routing-table](), [traffic-engineering](), [visibility]() ### AI overview This article explains BGP route choices, comparing default routes, full routes, partial routes, and customer routes. It describes the tradeoffs between small routing tables, Internet visibility, traffic engineering control, and router resource requirements. ### Source excerpt 5 minute read time.Justin Wilson j2sw.com When you configure a BGP session, one of the first questions is what routes you actually want to receive. If you have ever filled out a questionnaire with Hurricane Electric or another transit provider, they ask you what "kind" of routes you want. In this article, I plan to ... Read more The post Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes appeared first on Justin Wilson (j2sw). ## How Passive Optical Networks (PON) Work DevFeed: [How Passive Optical Networks (PON) Work]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-22T12:35:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Networks](), [gpon](), [Internet](), [Ethernet](), [gateway](), [Security](), [Deployment]() Tags: [ethernet](), [fiber](), [ftth](), [gateway](), [gpon](), [internet](), [internet-architecture](), [isp](), [networks](), [passive-optical-network](), [pon](), [providers](), [provisioning](), [router](), [security](), [xgs-pon]() ### AI overview This tutorial explains how Passive Optical Networks (PON) deliver residential fiber Internet. It describes the roles of the OLT, passive optical splitters, ONTs, and the customer router or gateway, including how providers share feeder fiber among subscribers and provision authorized ONTs. ### Source excerpt If you've spent any time looking into fiber Internet, you've probably run across terms like GPON, XGS-PON, OLT, and ONT. These are all parts of what's called a Passive Optical Network, or PON. Most residential fiber providers use PON because it lets them connect alot of homes without having to pull a separate fiber from ... Read more The post How Passive Optical Networks (PON) Work appeared first on Justin Wilson (j2sw). ## osmo-ePDG - VoWifi Evolved Packet Data Gateway - osmo-epdg 0.1.2 released DevFeed: [osmo-ePDG - VoWifi Evolved Packet Data Gateway - osmo-epdg 0.1.2 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-07-22T09:00:22Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [gateway](), [changelog](), [version]() Tags: [bug](), [changelog](), [compiler](), [gateway](), [ipv6](), [issue](), [tracker](), [version]() ### AI overview Osmocom released osmo-epdg 0.1.2, an unstable release of its VoWifi Evolved Packet Data Gateway. The changelog lists IPv4/IPv6 support improvements, Diameter and GTP-related fixes, dependency updates, documentation changes, and test updates. ### Source excerpt Today we've released osmo-epdg 0.1.2. The changelog over 0.1.0 is as follows: osmo-epdg (0.1.2) unstable; urgency=medium [ clufn-sudo ] * Add required conversions for IPv6 and IPv4v6 support [ clufn ] * Enable the use of an UE requested IP type and address to be used for gtpv2 PDN Address Allocation [ Pau Espin Pedrol ] * gsup: Fix rx of AuthInfoReq without IP addr val * rebar.config: Update rebar3_diameter_compiler from 0.8.0 to v0.8.1 * dia/diameter_3gpp_ts29_173.dia: Fix trailing whitespace * dia/diameter_3gpp_ts29_273.dia: Fix trailing whitespace * dia/diameter_3gpp_ts29_229.dia: inherit only Line-Identifier * dia/diameter_3ggp_ts32_299.dia: Inherit RFC4005 instead of RFC7155 * dia: restrict AVPs inherited from RFC4005 * Remove duplicate 3GPP-AAA-Server-Name definition and break 3-way circular dependency * cosmetic: Fix typo in code documentation * aaa_ue_fsm: Avoid immediate stop of fsm during 2nd SWx RTR * aaa_diameter_swx: Avoid answering RTR with Success if already deregistering [ Alexander Couzens ] * s2b: set correct instance values for Bearers * diameter_3gpp_ts29_273_swx: add missing include for MAR * aaa_diameter_swx_tests: explicitly set Framed-IP-Address * aaa_diameter_swx_tests: use MAR record to improve readability [ Oliver Smith ] * editorconfig: new file [ Vadim Yanitskiy ] * rebar.config: use more recent rebar3_diameter_compiler * rebar.lock: use a more recent version of gen_netlink -- Oliver Smith Tue, 21 Jul 2026 14:12:41 +0200 osmo-epdg (0.1.1) unstable; urgency=medium [ Harald Welte ] * add notice about NLnet found ation to README.md * README.md: Use NLnet suggested language for funding acknowledgement * README.md: Update user manual section; we now have one. [ Oliver Smith ] * rebar.lock: update gtplib commit -- Oliver Smith Wed, 04 Dec 2024 15:24:46 +0100 ## Session revocations at scale DevFeed: [Session revocations at scale]() Original publisher: [Read original article]() Author: Llew Vallis Published: 2026-07-22T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [sessions](), [Cookies](), [Authorization](), [Caching](), [MySQL](), [scaling](), [gateway](), [Redis](), [reliability]() Tags: [backend](), [caching](), [cookies](), [gateway](), [mysql](), [permissions](), [redis](), [reliability](), [scaling](), [security](), [sessions]() ### AI overview Canva describes how it manages session revocations for hundreds of millions of users. The system keeps revocations in memory for fast gateway checks, while MySQL handles refresh-time lookups; the article explains how loading the cache during deployments created database load and discusses evaluating Redis as a caching solution. ### Source excerpt How Canva keeps hundreds of millions of user sessions fast and secure ## Apollo's New API IP Allowlist Policy DevFeed: [Apollo's New API IP Allowlist Policy]() Original publisher: [Read original article]() Author: David Glasser Published: 2026-07-15T12:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [API](), [Firewall](), [gateway](), [Network](), [configuration]() Tags: [announcement](), [api](), [configuration](), [firewall](), [gateway](), [graphos](), [infrastructure](), [installation](), [network](), [operational](), [published](), [router](), [schema](), [trust-center]() ### AI overview Apollo has published an API IP Allowlist Policy for GraphOS Router and Apollo Gateway deployments that restrict outbound access by IP address. The policy covers Apollo Uplink endpoints, documents their current IP addresses, and promises at least 60 days' notice before adding new IPs. Apollo also plans to add a second IP per covered service no earlier than September 16, 2026. ### Source excerpt Restricting outbound traffic by IP? GraphOS Router now needs a second Uplink IP allowlisted before September 16, 2026. See what Apollo's new policy covers. ## What an AI Agent Failure Revealed About Model Tradeoffs, Evals, and Traces DevFeed: [What an AI Agent Failure Revealed About Model Tradeoffs, Evals, and Traces]() Original publisher: [Read original article]() Author: Sergiy Dybskiy Published: 2026-07-01T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [Traces](), [Artificial Intelligence](), [Prompt Engineering](), [vercel ai sdk](), [gateway]() Tags: [agent](), [ai](), [eval](), [evals](), [model](), [tool](), [tools](), [trace](), [traces]() ### AI overview An experiment with an AI-powered conference schedule builder showed that an agent could invent speakers, falsely claim to have retrieved them from an API, and appear grounded because a tool had run. The article discusses model tradeoffs, evaluation limitations, and the value of inspecting agent traces. ### Source excerpt I gave the free tier a cheaper model and it invented conference speakers who don't exist. What that taught me about model tradeoffs, evals, and reading agent traces. ## Strategies for Migrating from a Monolith to Microservices DevFeed: [Strategies for Migrating from a Monolith to Microservices]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-06-23T07:55:12Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Architecture & Design](), [microservices architecture](), [migration](), [legacy systems](), [gateway]() Tags: [api-gateway](), [architecture](), [automated](), [big-bang](), [feature-flags](), [incremental](), [legacy-systems](), [microservices](), [migration](), [monolith](), [parallel](), [rewrite](), [strategies](), [testing]() ### AI overview This tutorial outlines patterns for gradually moving from a monolithic architecture to microservices. It describes the Strangler Fig Pattern, Parallel Run Pattern, and Collaborator Pattern, covering techniques such as API gateways, incremental migration, traffic splitting, feature flags, and automated comparison testing. ### Source excerpt Top Strategies ## Kubernetes 网络深度系列 DevFeed: [Kubernetes 网络深度系列]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-04-03T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [Linux](), [eBPF](), [VXLAN](), [gateway](), [nginx](), [traefik](), [Grafana]() Tags: [ebpf](), [gateway](), [grafana](), [index](), [k8s](), [kubernetes](), [linux](), [net-11](), [networking](), [nginx](), [return](), [series](), [service-mesh](), [traefik](), [vxlan]() ### AI overview A Chinese tutorial series explains Kubernetes networking from the Linux network stack through virtual devices, routing, tunnels, eBPF, CNI plugins, Services, security policies, service discovery, traffic management, performance tuning, and troubleshooting. It includes packet captures, code, and kernel-source references, with comparisons of major CNI and ingress approaches. ### Source excerpt 从 Linux 网络栈的第一个字节到多集群联邦网络的最后一跳----用代码、抓包和内核源码把 Kubernetes 网络讲透 ## Unifying Internal APIs: A Different Use Case for GraphQL Gateways DevFeed: [Unifying Internal APIs: A Different Use Case for GraphQL Gateways]() Original publisher: [Read original article]() Author: Angel Svirkov Full-Stack Software Engineer @ trivago GitHub profile Linkedin profile Published: 2026-03-27T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [GraphQL](), [gateway](), [Tooling](), [Architecture & Design](), [Microservices]() Tags: [admin](), [agents](), [apis](), [architecture](), [artificial-intelligence](), [backend](), [crud](), [engineering](), [gateway](), [graphql](), [tooling]() ### AI overview This article describes how trivago used GraphQL Mesh to unify fragmented internal APIs into a gateway for administration, CRUD operations, reporting, and data exploration. It covers the architecture, implementation challenges encountered over six years in production, and possible future uses involving AI agents. ### Source excerpt Most GraphQL Gateway discussions focus on public-facing APIs and multi-client architectures. This article explores a different axis--using GraphQL Mesh to stitch internal services into a unified gateway powering admin tooling. We share implementation details, honest challenges from six years in production, and a forward-looking perspective on how AI agents could leverage the unified graph. ## Operating Trino at Scale With Trino Gateway DevFeed: [Operating Trino at Scale With Trino Gateway]() Original publisher: [Read original article]() Author: Prakhar Sapre Published: 2026-03-24T12:01:00Z Content type: article Language: en Sources: [Expedia]() Topics: [gateway](), [Load Balancing](), [Routing (disambiguation)](), [data analytics](), [Authentication](), [SQL]() Tags: [analytics](), [authentication](), [clusters](), [concurrency](), [data-science](), [downtime](), [gateway](), [load-balancer](), [load-balancing](), [open-source](), [sql](), [trino](), [trino-gateway](), [trinos]() ### AI overview This article explains how Trino Gateway routes queries across multiple Trino clusters and centralizes routing, authentication, load balancing, monitoring, and cluster management. It describes the project's origins as Presto Gateway at Lyft and its role in supporting larger analytics platforms with more complex workloads and higher concurrency. ### Source excerpt Expedia Group Technology -- DataWorkload-aware routing for TrinoPhoto by Joseph Barrientos on Unsplash Trino -- a fork of PrestoSQL -- is a powerful tool in modern data analytics, enabling organizations to query large datasets quickly and efficiently. As a distributed SQL query engine, Trino provides fast, scalable insights without requiring data relocation. While Trino is robust on its own, its capabilities are further enhanced when paired with a Gateway, which introduces features such as query routing, strong security, and streamlined cluster management. A brief overview The Gateway project originated at Lyft as Presto Gateway, serving as a proxy and load balancer for PrestoDB. It was later forked and integrated into the Trino ecosystem, with contributions from various organizations and the open-source community. The Gateway serves as a central point for managing and routing queries, providing a unified interface for users and administrators. As organizations scale their analytics platforms, they often encounter challenges such as increased query complexity, higher concurrency, and the need for specialized cluster configurations. Directing users to specific cluster endpoints becomes impractical as the user base grows. A Gateway addresses these challenges by routing queries to the most appropriate clusters based on workload, improving efficiency and responsiveness. The Gateway acts as a vital intermediary between users and the Trino query engine. By abstracting the complexities of distributed query execution, it manages critical functions such as routing, authentication, and load balancing across diverse backend clusters. This ensures that queries are efficiently directed to the optimal processing cluster. With an intuitive user interface, the Gateway transforms what was once a convoluted process into a manageable and transparent experience empowering administrators with real-time insights and precise control over their backend cluster infrastructure. Whether it's mon ## Mintlify acquires Helicone to redefine AI knowledge infrastructure DevFeed: [Mintlify acquires Helicone to redefine AI knowledge infrastructure]() Original publisher: [Read original article]() Author: Han Wang Published: 2026-03-03T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [gateway](), [LLM observability](), [Artificial Intelligence](), [agent observability](), [Open Source]() Tags: [agentic-ai](), [ai](), [ai-gateway](), [announcements](), [llm-observability](), [observability](), [open-source]() ### AI overview Mintlify announces its acquisition of Helicone, an open source LLM observability platform and AI gateway. Helicone's team is joining Mintlify to help develop AI knowledge infrastructure, while Helicone will continue in maintenance mode with security updates, bug fixes, and new models. ### Source excerpt Mintlify is acquiring Helicone, the open source LLM observability platform and AI gateway. Helicone's team has been building at the frontier of agentic AI, and they're joining to help us build the next generation of AI knowledge infrastructure. ## netlab 1.9.6: Static Routes to Default Gateways DevFeed: [netlab 1.9.6: Static Routes to Default Gateways]() Original publisher: [Read original article]() Published: 2025-03-25T07:25:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [gateway](), [Python](), [Ubuntu](), [Networks](), [Package Management](), [upgrade]() Tags: [bug-fixes](), [dependencies](), [gateway](), [netlab](), [networks](), [python](), [release](), [ubuntu]() ### AI overview netlab 1.9.6 fixes installation problems caused by Python dependency conflicts on Ubuntu 24.04. The release also adds default gateways as valid next hops for static routes, improves IPv6 default-gateway processing, sets a 9500 MTU for libvirt bridge networks, and supports specifying Juniper vMX license files through device or node variables. ### Source excerpt Last week, I had to push out netlab release 1.9.6 to address a particularly nasty Python dependency hell to make netlab work (again) on Ubuntu 24.04 (more details). The release also brought these goodies (and a bunch of bug fixes): Add default gateway (including anycast- and VRRP gateway )as a valid next-hop for static routes Rewrite the default gateway processing and add IPv6 default gateways on links without anycast or VRRP gateways Set libvirt MTU to 9500 on bridge-based networks to avoid the "transparent fragmentation" on Linux bridges. Use device- or node variables to specify the Juniper vMX license file. Read more ... ## Heroku at TDX 2025: Empowering Developers for the Future DevFeed: [Heroku at TDX 2025: Empowering Developers for the Future]() Original publisher: [Read original article]() Author: Emily Todd Published: 2025-02-10T15:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [developer-relations](), [Slack](), [gateway]() Tags: [2025](), [agentforce](), [developer-tools](), [developers](), [dynos](), [elastic](), [event](), [events](), [heroku](), [heroku-connect](), [integration](), [integrations](), [news](), [platform](), [real-time](), [salesforce](), [slack](), [software-engineering](), [workshops]() ### AI overview Heroku previews its TDX 2025 sessions and activities in San Francisco, covering integrations with Agentforce and Salesforce technologies. The program includes topics such as Flow and Apex, Heroku Connect, MuleSoft Flex Gateway, Slack apps, custom code, and workshops and demos. ### Source excerpt TDX25 comes to San Francisco this March 5-6. Heroku, a Salesforce company, has a packed schedule with a variety of sessions and activities designed to enhance your knowledge of our platform and integrations with Agentforce and Salesforce technologies. Whether you're new to Heroku or a seasoned pro, there's something for everyone at this year's event. [...] The post Heroku at TDX 2025: Empowering Developers for the Future appeared first on Heroku. ## AWS API Gateway's Request Validation: Navigating the Quirks DevFeed: [AWS API Gateway's Request Validation: Navigating the Quirks]() Original publisher: [Read original article]() Author: Thomas Klein Published: 2024-08-09T12:07:11Z Content type: tutorial Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [API](), [gateway](), [JSON Schema](), [TypeScript](), [configuration](), [enum](), [HTTP]() Tags: [api](), [api-gateway](), [aws](), [aws-api-gateway](), [aws-lambda](), [enum](), [gateway](), [handler](), [http](), [json](), [json-schema](), [middleware](), [middy](), [tests](), [type-safety](), [typescript](), [validation](), [zod]() ### AI overview This tutorial examines AWS API Gateway request validation. It explains that query-parameter presence is checked, but enum values may not be enforced, while POST and PUT payloads are validated with JSON Schema Draft 4. It also discusses generic error messages and TypeScript-based validation approaches. ### Source excerpt AWS API Gateway's request validation follows a specific set of rules that developers should be aware of when setting up their APIs. While it offers some validation features, it's important to understand its scope and limitations. Let's examine how it works with a common API configuration: parameters: - name: offerType in: query required: true description: RENT or BUY schema: type: string enum: - RENT - BUY With this configuration, API Gateway diligently checks for the presence of the query parameter, returning an HTTP 400 error if it's missing. However, it falls short when it comes to validating the actual value. Surprisingly, it would accept "KERMIT" without batting an eye, despite the clear enum specification. This behavior, while documented, can be a source of frustration for developers expecting more comprehensive validation. Interestingly, API Gateway shows more validation prowess with POST and PUT requests. It validates request payloads using JSON Schema Draft 4, demonstrating a somewhat inconsistent approach to input validation across different HTTP methods. Even when it does catch an error, API Gateway's feedback is less than illuminating. Instead of specific error details, you're met with a generic {"message": "Invalid request body"}. For more information, you'll need to dig into the associated log streams, which isn't ideal for surfacing error details in API responses. Example output in AWS console from a failed request validation when a body request validator is setup. API Gateway's validation is handy, but it leaves a lot to be desired. Developers often need to add extra checks for a truly robust API. While API Gateway supports various integrations and Lambda languages, let's focus on TypeScript. TypeScript's strong typing and runtime checks can catch issues early, sparing your users from cryptic error messages. Let's explore how to use this to make your API smarter and your users happier. Option 1: DIY Validation (AKA The "I've Got Trust Issues" Approac ## Mastering API Gateway Integration: Salesforce, Heroku, and MuleSoft Anypoint Flex Gateway DevFeed: [Mastering API Gateway Integration: Salesforce, Heroku, and MuleSoft Anypoint Flex Gateway]() Original publisher: [Read original article]() Author: Julián Duque Published: 2024-07-29T18:00:00Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [gateway](), [Heroku](), [API](), [Deployment](), [Security](), [Microservice](), [Cloud](), [Authentication](), [Authorization](), [Encryption](), [rate-limiting](), [Latency]() Tags: [api](), [api-gateway](), [api-security](), [apis](), [app-architecture](), [authentication](), [authorization](), [cloud](), [deployment](), [developer-tools](), [encryption](), [engineering](), [heroku](), [integration](), [integrations](), [latency](), [microservices](), [rate-limiting](), [salesforce](), [security]() ### AI overview A tutorial on deploying MuleSoft Anypoint Flex Gateway on Heroku to expose private APIs and microservices. It describes the gateway's API management, security, traffic management, rate limiting, and scalability capabilities, with possible integration with Salesforce. ### Source excerpt In today's fast-paced digital world, companies are looking for ways to expose their APIs and microservices to the internet while enhancing their overall API security. MuleSoft Anypoint Flex Gateway is a powerful solution that solves this problem. Let's walk through deploying the Anypoint Flex Gateway on Heroku in a few straightforward steps. You'll learn how [...] The post Mastering API Gateway Integration: Salesforce, Heroku, and MuleSoft Anypoint Flex Gateway appeared first on Heroku. ## Streamlining GraphQL Service Testing with Karate DevFeed: [Streamlining GraphQL Service Testing with Karate]() Original publisher: [Read original article]() Author: Armin Aminian SRE; Cloud Native technologies GitHub profile Linkedin profile Published: 2024-07-08T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [GraphQL](), [Testing](), [Microservice](), [API](), [gateway]() Tags: [api](), [architecture](), [backend](), [devops](), [gateway](), [graphql](), [integrity](), [microservice-architecture](), [quality-assurance](), [release-engineering](), [rest](), [schema](), [services](), [testing]() ### AI overview The article describes trivago's move from a GraphQL monolith to a federated microservice architecture and explains the testing challenges this creates. It covers complex nested queries, schema validation, relationships, data integrity, and GraphQL's partial-data error responses. ### Source excerpt Over the last year trivago refactored the existing GraphQL monolith and moved to a microservice architecture, in what is also known as a federated setup. Federated GraphQL, as championed by Apol... ## How a sports betting platform used CockroachDB for multi-state compliance DevFeed: [How a sports betting platform used CockroachDB for multi-state compliance]() Original publisher: [Read original article]() Author: Michelle Gienow Published: 2024-02-09T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Sports](), [Databases](), [real-time](), [Amazon Web Services](), [gateway](), [PostgreSQL]() Tags: [aws-outposts](), [cockroachdb](), [compliance](), [consistency](), [database](), [gateway](), [postgresql](), [sports](), [switching]() ### AI overview This article describes how a North America-based sports betting platform designed a multi-state architecture to meet performance, consistency, and data-locality requirements. It explains how CockroachDB, AWS Outposts, database gateway nodes, and geo-partitioning supported compliance while reducing the complexity of operating separate databases in each state. ### Source excerpt The challenges facing sports betting platforms are rigorous: they have to be fast and consistent in a way that's similar to high-frequency trading platforms. At the same time, they have a variety of data-locality requirements to comply with depending on which states or countries they serve. In this blog, we'll look at a real-world example of a North America-based sports betting platform that designed a gaming and sports betting architecture that not only meets the performance, consistency, and compliance requirements of the industry; but also enabled the business to swiftly enter new regional markets without requiring a massive engineering effort. ## How Intuit Handled their Busiest Time of Year with Apollo Router DevFeed: [How Intuit Handled their Busiest Time of Year with Apollo Router]() Original publisher: [Read original article]() Author: Ishwari Lokare Published: 2024-01-29T07:30:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [GraphOS](), [API Platform](), [gateway](), [Architecture & Design](), [Microservice]() Tags: [announcement](), [api-platform](), [apollo](), [architecture](), [gateway](), [go](), [graphos](), [graphql](), [microservices](), [microservices-architecture]() ### AI overview The article describes how Intuit moved from multiple internal GraphQL gateways toward a single supergraph powered by Apollo GraphOS and Apollo Router. The transition was intended to improve self-service, standards compliance, performance during seasonal traffic peaks, and supergraph management, while the work remained ongoing. ### Source excerpt Millions of small to midsize businesses turn to Intuit's Quickbooks to manage their accounting, payroll, tax, and more. It is overwhelmingly the most popular accounting software on the market today. Intuit serves 100 million individuals and businesses through its leading products TurboTax, Credit Karma, QuickBooks and Mailchimp. ## Deploying the Apollo Router at Apollo DevFeed: [Deploying the Apollo Router at Apollo]() Original publisher: [Read original article]() Author: Gary Pennington Published: 2023-11-06T12:32:40Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [gateway](), [Kubernetes](), [Resilience](), [Scalability](), [Development]() Tags: [announcement](), [apollo](), [development](), [gateway](), [helm](), [javascript](), [kubernetes](), [logging](), [production](), [resilience](), [router](), [scalability](), [typescript]() ### AI overview Apollo describes its internal migration from Apollo Gateway to Apollo Router for the Apollo Studio graph across development, staging, and production. The article discusses configuration, custom extensions, container and Helm-based deployment, and expected improvements in resilience, scalability, responsiveness, and resource consumption. ### Source excerpt Apollo doesn't just build Federation - we use it internally as well. Like many of our customers, we recently upgraded a fleet of Apollo Gateway instances to Apollo Router. This fleet ran the superschema for our "Apollo Studio" graph in multiple variants: development, staging, and production. Our team recently upgraded to the Apollo Router with very positive results which we'd like to share alongside some helpful tips. [Next page]()