In our third and final part of The Enterprise Architect's Intro to Microservices, we again welcome Lightbend CTO/co-founder and Akka creator Jonas Bonér to continue where we left off in the six characteristics of Reactive Microservices presented earlier with a simple premise (in the spirit of Carl Hewitt): one microservice is no microservice–they come in systems.
As any Enterprise Architect will come to understand, to exploit reality we need to live and operate within its constraints––accepting that time is relative, information has latency and so on––in order to bend these laws of concurrency and distribution. Here we review the real-life needs of systems of Microservices, including details on how to manage:
Oh, and if you missed the others, please also find:
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:
