Podcast: Play in new window | Download (Duration: 13:53 — 13.9MB) | Embed
On today’s TechCast, Sujan Kapadia talks to yet another Scala person: James Roper (@jroper). Previously a core team member of the Play framework, James is now the tech lead of Lagom, a new Java-oriented micro-services framework introduced by Lightbend. He discusses it in depth in his ETE talk, Rethinking REST in a Microservices World, as well as in this conversation with Sujan.
This talk will explain the rationale behind CQRS/ES, how it fits the Reactive paradigm and the advantages regarding both the technology and business level.
Modern, cloud-native applications typically use a microservices architecture in conjunction with NoSQL and/or sharded relational databases. However, in order to successfully use this approach you need to solve some distributed data management problems including how to maintain consistency between multiple databases without using 2PC.
Modern, cloud-native applications typically use a microservices architecture in conjunction with NoSQL and/or sharded relational databases. However, in order to successfully use this approach you need to solve some distributed data management problems including how to maintain consistency between multiple databases without using 2PC.
The reactive paradigm is a wonderful thing. The basic idea is that a reactive application, as much as possible, is asynchronous from beginning to end. It should be event driven, fault tolerant, scalable and responsive. Writing an asynchronous application, however, has it’s own set of unique challenges. In this post I’ll demonstrate an approach we took to solve the challenge of maintaining a definite order, specifically when performing database updates in asynchronous code within an actor.
