I’m a software developer with nearly 20 years of industry experience. During the years I worked for companies large and small, in roles ranging from Software Engineer to Chief Architect. When away from work, I aim to maintain an active media career as public speaker and blogger. I’m speaking and writing on topics such as Microservices, Domain-Driven Design, and more. Alongside the media work, I have a keen professional interest in Distributed Systems, Software Architecture, and Software Design in general. In the remaining time, I read lots of books on various topics, fly R/C aircrafts, and rescue troubled cats and dogs.
Embracing Polyglot Persistence Via CQRS
Once it was easy to choose a database. But then NoSQL happened: whole new families of databases started popping up. Choosing the right one became a grueling task — different consistency models, querying options, scalability concerns, and more. But what if instead of choosing “the” database, you could leverage multiple databases and rip all their benefits? That’s what we did at Internovus.
At Internovus we chose the polyglot persistence model. We opted for using the right tool for the right job: RDMBS, Search Engines, Document, Key/Value, and Columnar stores. But what (unexpectedly) made this approach work for us, was the “Command Query Responsibility Segregation” pattern.
In this session I’d like to share our experience of employing the CQRS pattern to find peace in the brave new world of polyglot persistence.
Date: October 11, 2018