Looking at the schedule of the day 2 talks, this was the other architecture talk I wanted to cover. When I’m looking at people in the community to learn from with regards to this topic, Eric Boyd is one of the names that comes to mind. These are some of the things that Eric touched on in his talk on messaging patterns and eventing for distributed systems.
Oh, another eCommerce example!
I don’t know what it is about us in this space, but eCommerce seems to be our go-to example. Joe was talking about Pink Socks by Joe. I use eCommerce in my EventStorming for Legacy Monoliths toward Microservices talk. Eric used eCommerce as an example in this talk. It’s apparently an eCommerce theme this time.
Messages vs Events
This is a question I hear often when talking with people – what’s the difference between a message and an event? As Eric put it – a message is a command with an expected outcode. An event is usually lightweight and more likely to be in a “fire and forget” situation.
The CAP Theorem captures critical points in talking about distributed system design. CAP stands for Consistency, Availability and Partition tolerance. These were points that Eric mentioned may come up as we explore the patterns.
The main focus of this talk involved messaging patterns. These are the main patterns that Eric referred to:
This was the 2nd architecture talk that I caught today, and it too was loaded with a lot of information. It was good to learn about these patterns in a very relatable scenario. If you ever need to catch a session on messages and events and Eric Boyd is around, I recommend checking it out.