It has to do with how they are designed and the types of problems they aim to solve.
SQL databases are designed around ACID properties. NoSQL databases, on the other hand, are designed to offer scalability, flexibility, and high performance across distributed systems.
This doesn't mean NoSQL databases completely abandon ACID properties; rather, they prioritize performance, scalability, and flexibility.
NoSQL follows BASE properties i,e Basically available , Soft State, Eventual Consistency.. for example.,. it may not fulfill consistency all the time but it will eventually become consistent. Hence, it sacrifices ACID properties but not fully!
I write about Deep System design,Engineering, tech, how to build things in tech at a deeper level, AI/ML inference, Benchmarks, LLMs and How to Quants, please checkout some of my posts ( more than 370000 reads) -
Amazing article, concise and clear. I agree these are the types of trade-offs one should keep in mind while designing large scale systems.
Could you clarify how read through and write through caches are trade-offs? Can a system use both the strategies while reading from and writing to a cache?
Thanks, Essence of this article is quite valueable
Thanks Nigam!
Great Effort! The language is simple and gives a quick understanding.
Simplest explanations. Thank you Ashish.
you are most welcome!
Absolutely fantastic content, thank you!
Sir how does NoSQL sacrifices ACID properties but the SQL does not? I am unable to catch up.
It has to do with how they are designed and the types of problems they aim to solve.
SQL databases are designed around ACID properties. NoSQL databases, on the other hand, are designed to offer scalability, flexibility, and high performance across distributed systems.
This doesn't mean NoSQL databases completely abandon ACID properties; rather, they prioritize performance, scalability, and flexibility.
Oohh... Now I get it!! Thank you very much sir
NoSQL follows BASE properties i,e Basically available , Soft State, Eventual Consistency.. for example.,. it may not fulfill consistency all the time but it will eventually become consistent. Hence, it sacrifices ACID properties but not fully!
Okay sir! Got it! Thank you very much!!!!
Nice one. Great to connect with you.
I write about Deep System design,Engineering, tech, how to build things in tech at a deeper level, AI/ML inference, Benchmarks, LLMs and How to Quants, please checkout some of my posts ( more than 370000 reads) -
https://howtosystemdesigneverything.substack.com/
https://aiinferenceandoptimizations.substack.com/
[Important AI Inference Pulse #4] KV Cache: The One Piece of Memory That Can Eat an Entire Expensive Chip — Just By Remembering- How It Actually Works
https://aiinferenceandoptimizations.substack.com/p/important-ai-inference-pulse-4-kv?r=14q3sp
[Bookmark : Most Important] Top System Design and Engineering Post Mortem Weekly Round Up : https://howtosystemdesigneverything.substack.com/p/bookmark-most-important-top-system?r=14q3sp&utm_campaign=post-expanded-share&utm_medium=web
[Celebration Time : Giveaway] 400,000 Reads, 5200 subscribers, System Design, ML System Design Playlist Gone Viral including Case studies [Bookmark]
https://howtosystemdesigneverything.substack.com/p/celebration-time-giveaway-400000?r=14q3sp&utm_campaign=post-expanded-share&utm_medium=web
Amazing article, concise and clear. I agree these are the types of trade-offs one should keep in mind while designing large scale systems.
Could you clarify how read through and write through caches are trade-offs? Can a system use both the strategies while reading from and writing to a cache?