AppSync doesn’t allow unauthenticated API calls. To allow users to call your API without first authenticating themselves, you must mimic the behaviour using one of the available authorization methods. In this post, let’s look at three ways to implement unauthenticated GraphQL operations with AppSync and their pros & cons. The post AppSync: how to implement unauthenticated operations appeared first on theburningmonk.com.

Versioning an API built with API Gateway and Lambda isn’t as straightforward as it sounds. You need to support multiple live versions without piling up technical debt or duplicating infrastructure. In this post, we look at practical strategies for managing API versions - from duplicating functions to routing by headers - and weigh the trade-offs so you can choose the right approach for your team. The post How to version APIs with API Gateway and Lambda appeared first on theburningmonk.com.

When we talk about event-driven architectures, we often focus on things like loose coupling, scalability and DDD. But under the hood, the way consumers receive events matters just as much. And it usually comes down to one of two models: push vs poll. Your choice dictates what service(s) you use and how you handle errors. So, in this article, let’s compare the two models and understand their pros & cons. The post Understanding push vs poll in event-driven architectures appeared first on theburningmonk.com.

Serverful (i.e. paying for uptime) services like RDS makes working with ephemeral environments more difficult and poses a cost concern. In this artcile, let's see how Neon's Serverless Postgres database solves this problem and how we can clone an existing database instantly by branching from it. We will see how Neon differs from Aurora Serverless v2 and give you a step-by-step guide on how to use Neon with ephemeral environments in both your day-to-day feature development work, as well as in CI/CD pipeline[...]

What if you don't have to worry about event versioning or catching breaking changes anymore? What if event consumers are no longer coupled to the schema of the event and instead, subscribe to their semantics? I discovered an exciting new way to manage event schemas that will blow your mind! The post Bye bye schema coupling, hello semantic coupling appeared first on theburningmonk.com.