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...
A blog about all things data and data processing issues and interests. SQL, NoSQL, flexible schema, scale-up, scale-out, transactions, high availability.