I have read a lot of system design articles but this one is very clear explanation of everything , how should you approach a decision. This article is very very good.
A really nice article,just one question though, writes for an e-commerce system are not just internal users right if we purchase a product ,every purchase should update the inventory so is that 99 percent to 1 percent split the correct representation?
I have read a lot of system design articles but this one is very clear explanation of everything , how should you approach a decision. This article is very very good.
thanks
A really nice article,just one question though, writes for an e-commerce system are not just internal users right if we purchase a product ,every purchase should update the inventory so is that 99 percent to 1 percent split the correct representation?
Great question, purchases are writes too.
In many systems, browsing, search, product pages, and recommendations still create far more traffic than product mutations or completed purchases.
But the important distinction is this:
Not all writes have the same role.
Catalog writes are usually internal/admin flows.
Purchase writes are customer-facing and critical.
Those should go through the correctness path: primary DB, transactions, inventory checks, idempotency, and clear failure handling.
Mt recommendation is: measure the hot path first, then decide which reads can be fast and which writes must be strongly protected.
Explained in detail thanks for sharing
Glad it helps!