Lagom is an open source JVM microservice framework. It's been designed from the ground up for doing just that - building microservices. Given that the JVM has not been a microservice stronghold so far, that alone is reason enough for a closer look.
But not only that, the creators desribe it as being "highly opinionated". The natural question is, then - what are those opinions, exactly? We will explore them, and the related concepts:
Use context bounds as boundaries for services! (Domain Driven Design)
The event log is the book of record! (Event Sourcing)
Separate the read and write sides! (CQRS)
Microservices, too, need to be elastic and resilient! (Reactive)
Developer experience matters! (The Lagom development setup)
At the end, you should have a good understanding of why things in Lagom are the way they are, and what to expect if you decide to build microservices with it.
YOU MAY ALSO LIKE:
- One more reason to learn Scala: Scala.js (SkillsCast recorded in June 2014)
- Azure DevOps (in Online on 15th July 2020)
- Building and Leading Remote Teams (in Online on 19th August 2020)
- Abstract Data Types In The Region Of Abysmal Pain, And How To Navigate Them (SkillsCast recorded in September 2019)
- Keynote: It’s a Trap! Vendor Lock-in and the Cloud (SkillsCast recorded in September 2019)
Implementing Microservices with Lagom
Lutz Huehnken is a Solutions Architect at Lightbend. He's been working in professional software development since 1997, and has successfully deployed major web applications for clients in different fields (retail, logistics, hospitality, finance). His current focus in on the development of reactive applications - responsive, scalable, resilient systems - with Scala, Akka and Play. Occasionally he speaks about this at conferences.