Example Architectures for Data Intensive Applications.
Keshav Murthy on June 15, 2020
In the book Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems, Martin Kleppmann has written about traits and trade-offs of elements of data infrastructure for modern applications. In that book, he has drawn “Figure 1-1. One possible architecture for a data system that combines several components”. This is an exploration that example and possible architecture with Couchbase.
Figure 1 below is the architecture from the book.
Let’s use a modern database like Couchbase which simplifies the infrastructure by providing scalable Cache, Database, Search, and Event processing within the same product. One bye one, we can replace each independent component with a scalable feature in Couchbase feature (
Again, let’s remove the unnecessary parts to get the new architecture. Here, we’ve exploited the Analytics service available within Couchbase.
This doesn’t mean everything can be simply rearchitected to use one or two products. The tendency of any infrastructure is to increase complexity. More components will increase complexity. This is a guide to continuously add, remove, and refactor the components to meet your business objective and to fight complexity.
- Posted in:Application Design, Best Practices and Tutorials
- Tagged in:application, Architecture, database, nosql, Scalability
Posted by Keshav Murthy
Keshav Murthy is a Vice President at Couchbase R&D. Previously, he was at MapR, IBM, Informix, Sybase, with more than 20 years of experience in database design & development. He lead the SQL and NoSQL R&D team at IBM Informix. He has received two President’s Club awards at Couchbase, two Outstanding Technical Achievement Awards at IBM. Keshav has a bachelor’s degree in Computer Science and Engineering from the University of Mysore, India, holds ten US patents and two US patents pending.
Sponsored by Couchbase