# API Gateway Published articles for API Gateway. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Model routing with Google Cloud API Gateway DevFeed: [Model routing with Google Cloud API Gateway]() Original publisher: [Read original article]() Author: Mak Ahmad; Sanjay Pujare Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Amazon API Gateway](), [Model Routing](), [Google](), [Cloud](), [OpenAPI Specification](), [Serverless](), [Claude](), [OpenAI]() Tags: [ai-gateway](), [api-gateway](), [claude](), [cloud](), [google](), [model-routing](), [models](), [openai](), [openapi](), [serverless]() ### AI overview Google Cloud API Gateway adds model routing in Public Preview, providing a serverless, OpenAI-compatible endpoint that dynamically routes requests to Gemini, Claude, or OpenAI OSS-GPT. Developers can configure routing in OpenAPI specifications, centralize model changes, and separate application authentication from backend model credentials. ### Source excerpt Google Cloud API Gateway now offers a model routing feature in Public Preview, allowing developers to dynamically route traffic to models like Gemini, Claude, or OpenAI OSS-GPT without hardcoding endpoints or managing open-source proxies. Developers can easily configure these routing rules directly within their OpenAPI 3.x specifications by mapping virtual model names to specific backend targets on a shared host. Once deployed, the Gateway acts as a serverless ingress layer that accepts standard OpenAI-compatible requests, automatically transcodes the payload to the native schema of the target model, and routes the traffic on the fly. ## Agent Gateway: The Next Evolution of the API Gateway DevFeed: [Agent Gateway: The Next Evolution of the API Gateway]() Original publisher: [Read original article]() Author: Gbadebo Bello Published: 2026-09-10T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [AI Agent](), [Architecture & Design](), [Artificial Intelligence](), [Routing (disambiguation)](), [Authentication](), [Authorization](), [observability]() Tags: [agent-gateway](), [ai](), [ai-agents](), [api](), [api-101](), [api-gateway](), [architecture](), [authorization](), [editor-s-picks](), [fabric-gateway](), [general](), [llm-gateway](), [mcp](), [mcp-gateway](), [observability](), [routing]() ### AI overview The article explains the emergence of the Agent Gateway as an architectural component for AI agents. It contrasts traditional API Gateways, which authenticate, govern, route, and deliver requests from clients that already know which API to call, with the needs of AI agents, which receive goals and may require broader governance across agentic workflows. ### Source excerpt API gateways are evolving for AI agents. Learn how the agent gateway governs identity, tools, memory, and policy across agentic workflows. Get early access. The post Agent Gateway: The Next Evolution of the API Gateway appeared first on Postman Blog. ## MCP Went Stateless: What Now? DevFeed: [MCP Went Stateless: What Now?]() Original publisher: [Read original article]() Author: Janet Wagner Published: 2026-09-03T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [Model Context Protocol (MCP)](), [Scalability](), [MCP Server](), [Architecture & Design](), [Security](), [Tool]() Tags: [ai](), [ai-agents](), [api-gateway](), [api-security](), [api-standards](), [artificial-intelligence](), [blog](), [cloud-native](), [developers](), [http](), [llm](), [mcp](), [mcp-server](), [model-context-protocol](), [scalability](), [security](), [strategy]() ### AI overview The article examines the shift to stateless MCP and its implications for scalability, state management, security, gateways, and MCP server architecture. ### Source excerpt The latest release of the Model Context Protocol (MCP) specification has created a lot of buzz in tech circles. Why? Primarily because this AI communication protocol has now gone stateless! This shift from stateful to stateless impacts how developers of MCP servers and AI tools use the protocol moving forward. In addition, the change impacts ... ## API Gateways, AI Gateways, and MCP Gateways: Are Enterprises About to Pay Twice Again? DevFeed: [API Gateways, AI Gateways, and MCP Gateways: Are Enterprises About to Pay Twice Again?]() Original publisher: [Read original article]() Author: Rashmi Baberwal Published: 2026-08-12T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Model Context Protocol](), [Artificial Intelligence](), [Security](), [observability]() Tags: [ai](), [ai-agents](), [api](), [api-architecture](), [api-discovery](), [api-documentation](), [api-gateway](), [api-governance](), [api-management](), [api-monitoring](), [apis](), [artificial-intelligence](), [blog](), [generative-ai](), [infrastructure](), [mcp](), [observability](), [platforms](), [security](), [strategy]() ### AI overview The article examines how enterprises can prepare existing API infrastructure for AI gateways, MCP gateways, and agent-driven operations. It highlights prior investments in API management platforms, gateways, developer portals, security, observability, and API-first development. ### Source excerpt Over the last decade, enterprises invested heavily in API infrastructure. They purchased API management platforms, deployed gateways across business units and regions, built developer portals, introduced security and observability tools, and encouraged teams to adopt API-first development. The business case was compelling. APIs would make enterprise capabilities easier to reuse, shorten integration timelines, improve partner ... ## What is an Agentic Data Plane? DevFeed: [What is an Agentic Data Plane?]() Original publisher: [Read original article]() Author: Marc Millstone Published: 2026-07-09T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Artificial Intelligence](), [agent observability](), [Amazon API Gateway](), [AWS IAM](), [observability](), [SIEM, Security](), [Amazon Web Services]() Tags: [agentic](), [agents](), [ai](), [ai-agents](), [api](), [api-gateway](), [aws](), [bedrock](), [enterprise](), [governance](), [iam](), [identity](), [identity-management](), [llm](), [models](), [observability](), [siem](), [thought-leadership](), [token](), [tool](), [tools]() ### AI overview The article defines an Agentic Data Plane as a governed governance and runtime layer between enterprise AI agents and the data, tools, identities, and models they access. It explains why existing IAM, API gateways, and observability or SIEM systems do not adequately govern agent-specific actions, identity propagation, model selection, token spending, policy enforcement, and end-to-end tracing. ### Source excerpt The Agentic Data Plane is the governance and runtime layer that connects your AI agents to everything they act on. Learn what it does, why existing tools can't replace it, and what to look for in an enterprise-grade one. ## 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 ## Service Mesh vs API Gateway (Part III) DevFeed: [Service Mesh vs API Gateway (Part III)]() Original publisher: [Read original article]() Author: Franco Fernando Published: 2026-06-20T09:02:00Z Content type: comparison Language: en Sources: [The Polymathic Engineer]() Topics: [Architecture & Design](), [API]() Tags: [api](), [api-gateway](), [mesh](), [patterns](), [vs]() ### AI overview This article compares service mesh and API Gateway patterns, explaining that they address different problems and can work best together. ### Source excerpt Two patterns that look similar, solve different problems, and work best together. ## AI gateways: why and how DevFeed: [AI gateways: why and how]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-05-31T00:00:00Z Content type: article Language: en Sources: [Nicolas Fränkel]() Topics: [Amazon API Gateway](), [LLMs](), [Artificial Intelligence](), [Routing (disambiguation)](), [Claude](), [Security](), [litellm](), [Caching](), [Scalability](), [Load Balancing](), [observability]() Tags: [ai](), [ai-gateway](), [anthropic](), [api-gateway](), [backend](), [caching](), [claude](), [claude-code](), [coding-assistant](), [decoupling](), [devstral](), [gateway](), [litellm](), [llm](), [llms](), [load-balancing](), [mistral](), [observability](), [open-source](), [routing](), [scalability](), [security](), [technical]() ### AI overview This article explains how AI gateways apply the API gateway pattern to AI clients and LLM backends. It discusses using a gateway to centralize model and provider management, governance, cost control, routing, caching, failover, load balancing, and observability, and considers routing Claude Code requests to another provider. ### Source excerpt Before working for 2 years on the Apache APISIX API gateway, I was mainly oblivious to API gateways. It's only by working with them that I understood their value. Decoupling the client and the server unlocks a lot of options: moving authentication to the API Gateway, securing APIs, deduplicating API requests, etc. In this post, I want to describe how the same pattern applies to AI. AI gateways AI gateways work in a similar way. ## Billing API Gateway Calls: Architecture for API as a Service DevFeed: [Billing API Gateway Calls: Architecture for API as a Service]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-18T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [API](), [Amazon API Gateway](), [Software as a service](), [telemetry](), [data]() Tags: [api](), [api-gateway](), [architecture](), [batching](), [build](), [guide](), [infrastructure](), [instrumentation](), [pipeline](), [pitfalls](), [saas](), [usage-based-billing]() ### AI overview A guide to designing an API call metering pipeline for API-as-a-service products. It covers gateway instrumentation, asynchronous batching, aggregation, customer attribution, failure handling, and reconciliation against gateway logs. ### Source excerpt Build a metering pipeline that bills API calls accurately at high volume. Architecture, batching, and pitfalls for API as a service products. ## Top 10 API Gateway Use Cases in System Design DevFeed: [Top 10 API Gateway Use Cases in System Design]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-04-12T12:00:32Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Amazon API Gateway](), [Architecture & Design](), [Microservices](), [API]() Tags: [api-gateway](), [microservices](), [monolith](), [system-design](), [use-cases]() ### AI overview An article about ten API gateway use cases in system design, particularly as systems evolve from monoliths to microservices. The supplied evidence does not detail the individual use cases. ### Source excerpt As your system evolves from a monolith to microservices, a pattern quickly emerges: every service starts rebuilding the same things. ## What is the BFF Pattern? DevFeed: [What is the BFF Pattern?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-07T08:41:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [BFF](), [Amazon API Gateway](), [backends](), [client](), [interface](), [resiliency](), [Orchestration](), [rate-limiting]() Tags: [api-gateway](), [authentication](), [backends](), [bff](), [cache-control](), [client](), [decoupling](), [mobile](), [rate-limiting](), [resiliency]() ### AI overview The article explains the Backends-for-Frontends (BFF) pattern, in which dedicated API gateways serve different client types such as web browsers, mobile apps, and public or partner APIs. It describes how BFFs tailor APIs, isolate client-specific logic, and support functions including rate limiting, authentication, header sanitization, and cache control. It also discusses benefits such as resiliency, client-specific optimization, and faster development, along with drawbacks including code duplication and increasing complexity. ### Source excerpt And when do you need it? ## Storage: 10x Larger Uploads, 3x Cheaper Cached Egress, and 2x Egress Quota DevFeed: [Storage: 10x Larger Uploads, 3x Cheaper Cached Egress, and 2x Egress Quota]() Original publisher: [Read original article]() Author: Inian Parameshwaran Published: 2025-07-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Amazon API Gateway](), [Caching](), [Terraform]() Tags: [3d](), [api](), [api-gateway](), [applications](), [cache](), [cdn](), [media](), [pricing](), [quotas](), [s3](), [saas](), [storage]() ### AI overview Supabase announces 500 GB file uploads for paid plans, cheaper cached egress, and increased cached and uncached egress quotas. The changes support large media files, user-generated data, 3D models, and archival workloads. ### Source excerpt Upload files up to 500 GB with significant egress cost reductions. ## Introducing the Serverless MCP DevFeed: [Introducing the Serverless MCP]() Original publisher: [Read original article]() Author: Serverless Team Published: 2025-04-17T00:00:00Z Content type: release Language: en Sources: [Serverless Blog]() Topics: [MCP](), [ide](), [Amazon API Gateway](), [AWS Lambda](), [debugging](), [Amazon Web Services](), [Monitoring]() Tags: [api-gateway](), [applications](), [aws](), [aws-lambda](), [cloud-computing](), [debugging](), [faas](), [function-as-a-service](), [ide](), [infrastructure-as-code](), [mcp](), [monitoring](), [news](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview The Serverless MCP is presented as a debugging tool that brings AWS Lambda, DynamoDB, and API Gateway state and logs into an IDE. It supports troubleshooting serverless applications with AI-assisted diagnostics and resource monitoring. ### Source excerpt The Serverless MCP is a powerful debugging tool that brings AWS Lambda, DynamoDB, and API Gateway state and logs directly into your IDE. Eliminate AWS console visits while troubleshooting serverless applications with AI-assisted diagnostics and resource monitoring. ## How Tinder Secures Its 500+ Microservices DevFeed: [How Tinder Secures Its 500+ Microservices]() Original publisher: [Read original article]() Author: Richard Oliver Bray Published: 2025-01-08T13:40:48Z Content type: tutorial Language: en Sources: [Hacking Scale by Better Stack]() Topics: [Microservices](), [Security](), [Architecture & Design](), [Amazon API Gateway](), [Authorization](), [Authentication](), [Routing (disambiguation)]() Tags: [api-gateway](), [authentication](), [authorization](), [mesh](), [microservices](), [routing](), [security](), [tls]() ### AI overview This article explains why Tinder's externally accessible services created security and maintenance challenges, and why the team built a customized API gateway to provide consistent session management, scalable configuration, and integration with its Envoy service mesh. ### Source excerpt Tinder's highly customised solution that fixed their microservice security chaos ## Canva incident report: API Gateway outage DevFeed: [Canva incident report: API Gateway outage]() Original publisher: [Read original article]() Author: Brendan Humphreys Published: 2024-12-20T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [incident](), [Amazon API Gateway](), [Deployment](), [Caching](), [Latency](), [Netty](), [Microservices]() Tags: [api](), [api-gateway](), [authentication](), [authorization](), [aws](), [caching](), [cloudflare](), [deployment](), [ecs](), [gateway](), [incident](), [infrastructure](), [java](), [latency](), [locking](), [microservices](), [outage](), [pir](), [post-incident-review](), [post-mortem](), [rate-limiting](), [report](), [s3]() ### AI overview Canva's incident report examines a November 12, 2024 outage that made canva.com unavailable for about 52 minutes. It attributes the outage to failures in the API Gateway cluster involving an editor deployment, a locking issue, and network latency between Cloudflare locations, and describes the incident timeline, mitigation, and prevention steps. ### Source excerpt An incident report for the Canva outage on November 12, 2024. ## Now in private beta: Gremlin Service Mesh Extension DevFeed: [Now in private beta: Gremlin Service Mesh Extension]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2024-12-04T00:00:00Z Content type: news Language: en Sources: [Gremlin Blog]() Topics: [Cloud Native Ecosystem](), [Resilience](), [Extension](), [Latency](), [Amazon API Gateway](), [Kubernetes](), [experiments]() Tags: [announcements](), [api-gateway](), [experiments](), [extension](), [gremlin](), [kubernetes](), [latency](), [mesh](), [resilience]() ### AI overview Gremlin announces a private beta for its Service Mesh Extension, which enables application-level targeting of specific services and HTTP paths for resilience testing in service meshes such as Istio and Kubernetes. The article explains how this complements IP-based infrastructure targeting and mentions Network and Latency experiments. ### Source excerpt Find out how to safely test applications and services behind service meshes with the Gremlin Service Mesh Extension. ## How Netflix Uses Throttling to Prevent 4 Big Streaming Problems DevFeed: [How Netflix Uses Throttling to Prevent 4 Big Streaming Problems]() Original publisher: [Read original article]() Author: Richard Oliver Bray Published: 2024-08-15T13:02:09Z Content type: article Language: en Sources: [Hacking Scale by Better Stack]() Topics: [Netflix](), [Streaming](), [Back end](), [Amazon API Gateway](), [Cloud]() Tags: [api-gateway](), [backend](), [cloud](), [netflix](), [streaming]() ### AI overview The article explains how Netflix uses throttling to shield content playback from backend problems, including network failures, underscaled services, retry storms, and faulty deployments. It also describes the role of an API Gateway in routing and monitoring requests. ### Source excerpt Netflix reveals their unconventional trick to keep viewers happy ## 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. ## Secure Java URL encoding and decoding DevFeed: [Secure Java URL encoding and decoding]() Original publisher: [Read original article]() Author: Jura Gorohovsky Published: 2023-08-14T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Programming](), [ASCII](), [Security](), [Amazon API Gateway](), [HTML](), [Routing (disambiguation)]() Tags: [acquisition](), [api](), [api-gateway](), [article](), [ascii](), [awareness](), [blog](), [code-security](), [developer](), [draftdotdev](), [engineering](), [how-to](), [html](), [java](), [programming](), [security](), [server](), [snyk-code]() ### AI overview This article explains URL encoding and decoding in Java. It describes percent-encoding characters outside the permitted URL character set, clarifies that URL encoding is not encryption, and discusses use cases such as HTML form input, external API calls, and API gateways. It also explains parsing, interoperability, and security risks caused by unencoded URLs. ### Source excerpt This article discusses Java, why URL encoding and decoding are important, and how to approach it properly. ## Vapor: Multi-level Subdomains DevFeed: [Vapor: Multi-level Subdomains]() Original publisher: [Read original article]() Author: Joe Dixon Published: 2023-06-28T12:35:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Vapor](), [AWS Certificate Manager](), [Deployment](), [Command-line interface](), [Amazon API Gateway]() Tags: [api-gateway](), [aws-certificate-manager](), [cli](), [deployment](), [feature](), [new-feature]() ### AI overview Vapor now supports deploying applications to multi-level subdomains. Users must explicitly include the subdomain in an AWS Certificate Manager certificate and Vapor domain configuration, then perform a full deployment using the Vapor CLI. ### Source excerpt Vapor has always made it straightforward to deploy your application to a custom domain, subdomain, or even wildcard subdomain. However, it's only been possible to utilize single-level subdomains - me... ## Connecting Block Business Units with AWS API Gateway DevFeed: [Connecting Block Business Units with AWS API Gateway]() Original publisher: [Read original article]() Author: Michael Weissbacher Published: 2023-05-18T13:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [Security](), [SPIFFE](), [SPIRE]() Tags: [api-gateway](), [aws](), [aws-api-gateway](), [engineering](), [network](), [security](), [spiffe](), [spire]() ### AI overview This article explains how Block integrates acquired companies with its internal service mesh using AWS API Gateway as an identity translation layer. The Farcars infrastructure maps acquisition-native identities and IAM-based SigV4 calls to Block-native mutual TLS, enabling isolated and reusable cross-mesh communication. ### Source excerpt Secure cross-mesh communication using in-mesh bastions ## Vapor: Managing DNS DevFeed: [Vapor: Managing DNS]() Original publisher: [Read original article]() Author: Joe Dixon Published: 2022-09-23T12:03:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Vapor](), [Deployment](), [Serverless](), [SSL](), [Amazon API Gateway](), [dashboards]() Tags: [api-gateway](), [deployment](), [dns](), [examples](), [getting-started](), [how-to](), [post](), [serverless](), [ssl](), [third-party](), [verification]() ### AI overview This post explains how to manage DNS for custom domains attached to Laravel Vapor projects, covering both Vapor-managed DNS and externally managed DNS. ### Source excerpt In this post, we'll discuss the different approaches to managing your DNS when attaching a custom domain to your Vapor project. ## Micro Service Events (AWS EventBridge vs. SNS) DevFeed: [Micro Service Events (AWS EventBridge vs. SNS)]() Original publisher: [Read original article]() Author: Kristian Müller Published: 2022-09-16T12:06:51Z Content type: comparison Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [event driven](), [Messaging](), [Amazon Web Services](), [Amazon Simple Queue Service (SQS)](), [Publish-subscribe pattern](), [Architecture & Design](), [AWS Lambda](), [Amazon API Gateway](), [DynamoDB](), [Amazon S3](), [TypeScript]() Tags: [api](), [api-gateway](), [architecture](), [aws](), [aws-eventbridge](), [aws-sns](), [data](), [data-processing](), [database](), [dynamodb](), [event](), [event-driven](), [eventbridge](), [eventbus](), [events](), [gateway](), [lambda](), [messaging](), [microservice-architecture](), [s3](), [sns](), [sqs](), [typescript]() ### AI overview This article examines Homegate's event-driven microservice architecture on AWS and compares Amazon SNS with EventBridge as messaging infrastructure. It describes how services use SNS, SQS, Lambda, API Gateway, DynamoDB, and S3, and explains that EventBridge has a different focus, so replacing SNS is not necessarily the right question. ### Source excerpt During the last few years, we've been busy rebuilding the Homegate platform in an event driven, micro service architecture based on AWS. One of the most important buildings blocks, or shall we rather say the mortar that connects the building blocks, is the way our services send events to each other. While Amazon offers its notification service SNS since more than 12 years; in 2019 it started a newcomer in the messaging bus field by introducing EventBridge. This was very interesting to us as we're using SNS a lot. Bus on a Bridge (Photo by "Blue Elf" on Wikimedia Commons) As EventBridge was introduced and gained traction we asked ourselves what advantaged we would gain by switching our SNS based service glue to EventBridge. Maybe this turned out to be the wrong question for us. Let's look at our system to see why. Micro Services Connected by SNS Homegate is connecting dozens of services via SNS right now. Those services range from single purpose Lambda functions written in TypeScript to database heavy services using Aurora or DynamoDB and Step Functions sending events to other services. Some of the services are also interfacing external APIs such as Salesforce or SendGrid. Here our Lambda functions can call APIs when needed. On the other hand, we have web services to be called as APIs by other systems and end users. This is mostly achieved via API Gateway. A typical service connects to the system by subscribing to events needed to fulfill its purpose. Those inbound SNS events are then ingested via SQS allowing for orderly data processing and DLQs to handle errors. Outgoing results are pushed back to the system in form of events to a SNS topics. As Marko Savic has pointed out, we're also utilizing S3 to store and replay those events if needed. Basic AWS Lambda function connected via SNS If we would replace the SNS topic by streams on the EventBridge we would initially gain the same functionality by utilizing SQS as well. However, EventBridge has a different focus. Let [Next page]()