Event-Driven Architecture

Bye bye schema coupling, hello semantic coupling

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!

Event versioning strategies for event-driven architectures

Event-driven architectures encourage loose coupling.

But we are still bound by lessor forms of coupling such as schema coupling. And here lies a question that many students and clients have asked me:

“How do I version my event schemas?”

In this post, let’s run through some common approaches and why they all suck to some degree and the two most important decisions you need to make.

EventBridge best practice: why you should wrap events in event envelopes

This article is about best practices for building event-driven architectures on AWS, with a focus on wrapping events in custom envelopes when using EventBridge.

While EventBridge provides metadata by default, a custom envelope allows for a standardized, consistent structure across all of your events, making it easier to manage and evolve the system over time.

By providing your own metadata, you can gain better interoperability between different services, end-to-end observability, idempotency control and versioning.

 

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close