As applications are being redesigned into microservices for a composable architecture – primarily driven by agility needs for faster evolution – a key thought line that evolved is the need for separation of state and business logic. What is missing in this thought line, however, is a clear understanding of the nuances of this separation.
In this brief session, we discuss key considerations when choosing a data architecture to support your journey into a composable architecture built on a microservices foundation. Topics covered, include:
- What are microservices?
- What it means to separate business logic and state
- Comparing data patterns for microservices
- What it means to have stateless containers, to scaling up and down
- The pitfalls of NoSQL for microservices
- And more
Dheeraj Remella, Chief Technologist, VoltDB