12 Comments
Mar 11Liked by Ashish Pratap Singh

Thanks, Essence of this article is quite valueable

Expand full comment
author

Thanks Nigam!

Expand full comment
Aug 7Liked by Ashish Pratap Singh

Great Effort! The language is simple and gives a quick understanding.

Expand full comment
May 23Liked by Ashish Pratap Singh

Absolutely fantastic content, thank you!

Expand full comment
Mar 17Liked by Ashish Pratap Singh

Simplest explanations. Thank you Ashish.

Expand full comment
author

you are most welcome!

Expand full comment

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?

Expand full comment

Sir how does NoSQL sacrifices ACID properties but the SQL does not? I am unable to catch up.

Expand full comment
author

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.

Expand full comment
Mar 12Liked by Ashish Pratap Singh

Oohh... Now I get it!! Thank you very much sir

Expand full comment

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!

Expand full comment

Okay sir! Got it! Thank you very much!!!!

Expand full comment