Why you should move to an Event-Driven Architecture

Learn how to decouple services and reduce complexity

Photo by Kelly Sikkema on Unsplash

Writing code is easy yet building software is hard. It doesn’t matter how good your code is, if the underlying architecture isn’t right you’ll still be left with bad software. Maybe not today. Maybe not a few months from now.

But eventually, you’ll be left with bad software.

In this post I’ll provide you with another tool for the toolkit that will help shape how you think about building software, to ensure it’s something you can be proud of in years to come.

What is Event-Driven Architecture?

An Event-Driven Architecture is as its name suggests, a way of building software so that events drive everything.

It’s based on the notion that if everything is an event, we then build things that respond to those events and maybe generate further events of their own. It’s a fairly simple premise but can often be a paradigm shift from how we usually design software.

I can bet that most of the time when you think about building software, you think of things in a Request Driven way. Don’t worry, if you do you’re not alone, I do too. In the rest of this post though I’ll teach you…