Events on the outside, on the inside and at the core

Recently, there was an interesting Twitter thread discussed the similarities between objects and microservices:

If we wrote “distributed multi-repository multi-language object-oriented code base” every time instead of saying “microservices”, we might have closer to the appropriate number of distributed multi-repository multi-language object-oriented architectures.
— Beth (@bethcodes) February 20, 2021

In particular, this tweet

+1. It’s very arguably, fractal. Going the other way, it’s common for a collection of Microservices to be hidden behind coarser-grained APIs for example. The interesting distinctions becomes when the calls between “modules” end up getting routed over non-local networks.
— Sam Newman (@samnewman) February 21, 2021

reminded me of a talk that I gave back in 2016 titled Events on the outside, on the inside and at the core.

Here is the abstract:

This presentation looks at the importance of events and the role that they play in applications. We describe how events are a key application integration mechanism and how they are used by applications to communicate with the outside world. You will learn how the microservices inside a system can use events to maintain data consistency. We discuss how easy it is to implement both of these mechanisms by developing your core business logic using an event-centric approach known as event sourcing.

This is an old talk and my thinking has changed over the past 5 years. In particular, event sourcing is now just one way to publish events. The other is, of course, to explicitly publish events. Moreover, event-based, choreography-based sagas are just one kind of saga - there are also orchestration based sagas.

Despite showing its age, this talk still has some useful ideas. It describes how there are commonalities between aggregates, services and enterprises from the perspective of event-driven software. Each publishes events when something notable occurs.

What’s more, this is just one specific example of how the same principles of modularity, encapsulation and coupling/cohesion occur at every level:

object
module
service
application/service cluster (encapsulated by an API Gateway/’BFF’)
enterprise

Each has an API consisting of operations and events that (hopefully) encapsulates the implementation.

Slides

Events on the outside, on the inside and at the core (jfokus jfokus2016) from Chris Richardson

Video

Follow @MicroSvcArch

About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.

Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.

Learn how to create a service template and microservice chassis

Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.

New virtual bootcamp: Distributed data patterns in a microservice architecture

My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!

It covers the key distributed data management patterns including Saga, API Composition, and CQRS.

It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.

The regular price is $395/person but use coupon JUNVCEJE to sign up for $195 (valid until February 1st, 2023). There are deeper discounts for buying multiple seats.

Learn more

Signup for the newsletter

For Email Marketing you can trust.

LEARN about microservices

Chris offers numerous resources for learning the microservice architecture.

Training classes

Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help your organization use microservices effectively.

Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.

Delivered in-person and remotely.