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)
- Extreme Java: Advanced Topics with Dr Heinz Kabutz (Online Course on 29th - 30th March 2021)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 19th - 21st April 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- Event-Driven Microservices: The Sense, Nonsense and a Way Forward (SkillsCast recorded in December 2020)
- Technologies for Microservices (SkillsCast recorded in December 2020)
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.