Dennis van der Stelt: Microservices and Distributed Systems - Episode 256

Dennis van der Stelt is a Software Architect who loves building distributed systems and the challenges they bring. To be better than the day before, he continuously searches for new ways to improve his knowledge of architecture and software development. What he learns he tries to share via numerous articles, presentations, and posts on his blog. If you want to chat, feel free to ping Dennis on Twitter at @dvdstelt.

Topics of Discussion:

[3:07] How did Dennis get into distributed systems?

[5:24] Helping customers with building distributed systems.

[7:00] Dennis describes the essence of distributed systems.

[9:07] The role of asynchronous messaging between components in distributed systems.

[12:38] Dennis shares a story about a panicked CEO when the database went down, and the lessons learned from the experience.

[14:44] Starting with synchronous distribution, and then moving to asynchronous when you find the benefit.

[16:05] The downsides of using asynchronous communication.

[17:28] Who decides what happens when things go wrong?

[22:34] What Amazon does right.

[27:18] Microservices and event-driven architecture — Jeffrey has yet to find a microservices expert!

[35:48] Thinking more about the domain model in vertical slices.