Part 2 of 3: The Enterprise Architect's Intro to Microservices

 

Had it with your hard-to-maintain, difficult-to-scale and overly-complex monolithic application? In this three-part series on Microservices for enterprise architects, we go over why it makes sense to learn about Microservices architectures, which are comprised of small, independent services and provide more flexibility than the traditional all-in-one systems that continue to dominate today’s enterprise landscape.

In Part 2 of our series for Enterprise Architects, Lightbend CTO and Akka creator Jonas Bonér shares the 6 characteristics of Reactive Microservices that matter for having responsive, elastic, resilient systems. In case you missed it, here is Part 1: Microservices, Monoliths, SOA and How We Got Here, with Kevin Webber.

Starting with importance of decomposing systems in discrete, isolated services that are decoupled in both time (i.e. concurrency) and space (i.e. distribution and mobility), and continuing with reiterating the need for asynchronous, message-driven communication and maintaining service mobility, we cover everything an Enterprise Architect needs to know about Reactive Microservices in these sections:

  • Isolate All the Things
  • 
Act Autonomously
  • Do One Thing, and Do It Well
  • Own Your State, Exclusively
  • Embrace Asynchronous Message-Passing
  • Stay Mobile, but Addressable 


Stay tuned for Part 3 of the series, when we welcome Jonas back to continue his deep dive into the nature of Microservices working together in systems (and the need to bend reality to make things happen).

SIGN UP FOR PART 3


Watch the full video

 

Read, code, meet up and start moving fast with Microservices

Or, if you want to start moving faster today, contact us to get started with Microservices and Lightbend technologies with our new Proof of Value (POV) service:

LEARN ABOUT POV SERVICES

 

Share


Comments


View All Posts or Filter By Tag