Why demanding ACID consistency cannot be a business requirement
In the previous post of this blog series, we discussed why strong consistency across multiple distributed data nodes is a bad idea. In this post, we will discuss why the “strong consistency is needed for business reasons” requirement is void.
Why you should avoid ACID consistency across multiple nodes
Well, of course ACID consistency exists – and it is a good thing that it exists. Thus, feel free to call the post title clickbait … ;)
Why standardization is a double-edged sword
Standardization is a two-edged sword. It has a value, but it also comes at a price.
Why ignoring NFRs is a bad idea
This post is about another “evergreen” in IT: The fallacy that only business features have business value.
Avoiding concept spill in API design
API design is a huge topic these days and you find a lot of information about how to design good APIs. Unfortunately, most of it is about tools or technology: Use Tool X for great APIs! Use technology Y and everything will be fine!
Web site and blog. Writing about IT most of the time.
I'm Uwe, travelling the world of IT for many years. Worked in many roles in and around IT. Sharing my thought, ideas and insights here. Explorer. Connector. Sharer. Coder. Writer. Human. More. Order may vary.
Learn More
