Thoughts on Event Driven Architectures

nwillc
nwillc
Nov 1 · 4 min read

This article is just some thoughts on event-driven architectures. There’s no code here, just observations, and take aways. To be clear, I’ll be using the term event-driven, but if you read the Wikipedia reference above, you’ll see I’m incorrectly commingling in message driven systems too.

TLDR;

This is a discussion about complexity, and a statement of the obvious that with great power comes great responsibility.

Keep the story going. Sign up for an extra free read.

You've completed your member preview for this month, but when you sign up for a free Medium account, you get one more story.
Already have an account? Sign in

nwillc

Written by

nwillc

Graybeard code monkey, started on an Apple IIe, got a CS degree in the 80’s, and coded my way through C, C++, Objective-C, Java. Now livin’ la vida Kotlin.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade