Skip to main content

Posts

Showing posts with the label ARCHITECTURE

MongoDB to Couchbase for Developers: Part 1: Architecture

  Introduction By any measure, MongoDB is a popular document-oriented JSON database. In the last dozen years, it has grown from its humble beginnings of a single lock per database to a modern multi-document transaction with snapshot isolation. MongoDB University has trained a large number of developers to develop the MongoDB database. There are many JSON databases now. While it's easy to start with MongoDB to learn NoSQL and flexible JSON schema, many customers choose Couchbase for performance, scale, and SQL. As you progress in your database evaluation and evolution, it's easier to start from what you know now. That's the idea for this series. Use your MongoDB knowledge to easily learn and eventually master Couchbase.  Don't despair if you don't know MongoDB do know any one of the RDBMS. This Oracle to Couchbase series will help you learn by comparison.  Many nations are known by their language: French, German, Spanish). Many databases are known for their language...

Sample Architecture using Amazon AWS, Microsoft Azure, Google GCP, MongoDB and Couchbase.

A drawing should have no unnecessary lines and a machine no unnecessary parts.                     William Strunk Jr. , Elements of Style 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 for data infrastructure while designing modern applications. He has given an example architecture for a data system that combines several components. I used this example for the article Example Architectures for Data-Intensive Applications . That article explored just the Couchbase features and functions. A recent twitter thread talked about how AWS has many databases , but most “half baked” services (not my characterization) compete for the same business as DynamoDB!  Could this be a paradox of choice ? Theory is, more choices do not usually lead to better outcomes. However, customers do vote with their dollars a...

Example Architectures for Data-Intensive Applications

    ...a drawing should have no unnecessary lines and a machine no unnecessary parts. -   William Strunk Jr. ,   Elements of Style 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 (  in red  ...