Microservices provide a number of benefits to developers and, ultimately, end-users of applications supported by microservices architectures. These include the ability to scale and develop each microservice independently, which enables increased release velocity. But microservices also introduce a number of challenges that developers need to address, especially if they are developing mission-critical transactional applications. Among these challenges is maintaining data consistency across a set of microservices. Enter command query responsibility segregation, or CQRS.
In this episode of Pivotal Insights, host Jeff Kelly dives into the topic of CQRS with Pivotal's own Kenny Bastani. Kenny, a Spring developer advocate, lays out the challenges CQRS helps microservices developers overcome, provides advice for implementing CQRS, and discusses the complexities that CQRS itself introduces to microservices applications.
News and Resources
- Read Kenny's blog post, Building Event-Driven Microservices Using CQRS and Serverless
- Watch Pivotal's Eitan Suez presentation from SpringOne Platform 2016, Where Does Apache Geode Fit in CQRS Architectures?
- Check out this CQRS microservice demo that runs and scales on Cloud Foundry from Pivotal's Ben Wilcock
- Visit http://pivotal.io/podcasts for show notes and other episodes.
- Download the episode and check us out on SoundCloud, subscribe to the feed directly, or on iTunes to have it automatically downloaded for you.
- Twitter: @jeffreyfkelly and @kennybastani
- Feedback: email@example.com
About the AuthorFollow on Twitter Follow on Linkedin