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!
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!!!!
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?