Discover and read the best of Twitter Threads about #DistributedSystems
Most recents (4)
🧵 My top 10 list of the IT books that helped me the most during my career.
1. Inside the Machine by Jon Stokes oreilly.com/library/view/i…
An insightful book to understand how a CPU works and help in earning some mechanical sympathy.
An insightful book to understand how a CPU works and help in earning some mechanical sympathy.
2. How Linux Works by @bricsuc oreilly.com/library/view/h… #linux
The best book, in my opinion, on Linux. A must-read as Linux today is absolutely everywhere. It provides most of the content every developer should be aware of.
The best book, in my opinion, on Linux. A must-read as Linux today is absolutely everywhere. It provides most of the content every developer should be aware of.
Implementing Distributed Transactions âš¡ [in a gist]
Distributed Transactions are not theoretical; they are very well used in many systems. An example of it is 10-min food/grocery delivery.
👇
Distributed Transactions are not theoretical; they are very well used in many systems. An example of it is 10-min food/grocery delivery.
👇
✨ The UX we want is: Users should see orders placed only when we have one food item and a delivery agent available to deliver.
A key feature we want from our databases is atomicity. Our storage layer can choose to provide it through atomic operations or transactions.
👇
A key feature we want from our databases is atomicity. Our storage layer can choose to provide it through atomic operations or transactions.
👇
We will have 3 microservices: Order, Store, and Delivery.
Important decision: Store services have food, and every food has packets that can be purchased and assigned.
Hence, instead of just playing with the count, we will play with the granular food packets while ordering.
👇
Important decision: Store services have food, and every food has packets that can be purchased and assigned.
Hence, instead of just playing with the count, we will play with the granular food packets while ordering.
👇
Be a level-triggered product manager.
A hack I learned working with distributed systems for a while is reacting towards a state not to every tiny little change.
#product #productdiaries #pmdiaries #productmanagement #distributedsystems
A hack I learned working with distributed systems for a while is reacting towards a state not to every tiny little change.
#product #productdiaries #pmdiaries #productmanagement #distributedsystems
In distributed-systems, also electronics, a system has two means to responds to recurring events over time to reach a desired state:
- Edge-triggering
- Level triggering.
en.wikipedia.org/wiki/Interrupt…
- Edge-triggering
- Level triggering.
en.wikipedia.org/wiki/Interrupt…
With edge-triggering, the system would react to every event be it major or minor by issuing detailed instructions on how to reach a state. With level-triggering, the "how" is not really relevant, what matters is that the desired state is reached matching the conditions specified.
Ever wonder how replication happens between Master and Replica? How changes on Master propagates to Replica?
This is a short thread of how it happens
#systemdesign #distributedsystems
🧵
This is a short thread of how it happens
#systemdesign #distributedsystems
🧵
Any write operation happening on the Master is logged in the Replication log file as an event. The format in which these events are logged in the Log file is called Replication Format.
The two common Replication formats:
- Statement-based format
- Row-based format
The two common Replication formats:
- Statement-based format
- Row-based format
✨ Statement-based Format
The Master records the operation as an event in its log, and when the Replica reads this log, it executes the same operation on its copy of data.
This way, the operation on the Master is executed on the Replica, which keeps it in sync with the Master.
The Master records the operation as an event in its log, and when the Replica reads this log, it executes the same operation on its copy of data.
This way, the operation on the Master is executed on the Replica, which keeps it in sync with the Master.
