Announcing Akka 24.05: More Security. More Performance. More Efficiency. Watch the Webinar Replay
cloud-native event-sourcing cqrs akka

Designing Events-First Microservices For A Cloud Native World

One Microservice Is Nothing...They Come In Systems

View on Slideshare

If you’re a human being (or meerkat, chimpanzee, bee, etc.) reading this, then you know that we tend to thrive best by collaborating in a community/system, not in isolation.

Similarly, in software development a single service is not terribly useful by itself—services come in systems, and become useful only when they can collaborate as systems. As soon as they start collaborating, we need ways to coordinate events and commands across a distributed system using a network that is inherently unreliable!

In this talk by Jonas Bonér, Lightbend CTO/Co-Founder and creator of Akka, we will explore the nature of events, what it means to be event-driven, and how we can unleash the power of events and commands by applying an events first, domain-driven design to microservices-based architectures. Specifically, we will discuss:

  • A solid theoretical understanding of how to design systems of event-driven microservices.
  • Practical tools and techniques you can use to reap the most benefit from that design, as well as, most importantly, what to avoid along the way.
  • How an events-first design approach to building microservices can increase certainty, resilience, scalability, traceability, and reduce risk compared to other techniques.

Watch The Full Presentation (~60 Min)

Watch on YouTube

Get The Free O'Reilly EBook By Jonas Bonér

If you're looking to learn more about this topic, then download this free O'Reilly book Reactive Microsystems: The Evolution of Microservices at Scale. Inside, you'll see strategies and techniques for building scalable and resilient microservices, helping you work your way through the evolution of a scalable microservices-based system.



The Total Economic Impact™
Of Lightbend Akka

  • 139% ROI
  • 50% to 75% faster time-to-market
  • 20x increase in developer throughput
  • <6 months Akka pays for itself