Distributed Systems are important for building scalable, fault-tolerant, and highly available systems.
Good compilation, Saurabh.
Thanks for the mention!
Thanks Raul. Keep those amazing articles coming!
Nice one, this will help everyone with their vocabulary for system design document reviews and interviews
Thanks Fran
Great overview of Distributed System Design Patterns! I've used the following patterns:
- Ambassador
- CQRS Pattern
- Pub/Sub Pattern
I might have used some other patterns but not in distributed systems:
- Event Sourcing (keeping the logs of transactions in a DB to reconstruct account balance)
- Sharding (with MongoDB, but I haven't had to implement this manually)
The sidecar and the leader pattern are things I've never used.
Thanks for the mention, Saurabh!
I think you've already used the most important ones. Sidecars are quite rare as far as I've seen. Also, the leader pattern is mostly used by databases so we might anyways end up using them.
Thanks Akos!
That's a great breakdown, Saurabh! And thank you for the mention, friend!
Thanks Petar
Good compilation, Saurabh.
Thanks for the mention!
Thanks Raul. Keep those amazing articles coming!
Nice one, this will help everyone with their vocabulary for system design document reviews and interviews
Thanks Fran
Great overview of Distributed System Design Patterns! I've used the following patterns:
- Ambassador
- CQRS Pattern
- Pub/Sub Pattern
I might have used some other patterns but not in distributed systems:
- Event Sourcing (keeping the logs of transactions in a DB to reconstruct account balance)
- Sharding (with MongoDB, but I haven't had to implement this manually)
The sidecar and the leader pattern are things I've never used.
Thanks for the mention, Saurabh!
I think you've already used the most important ones. Sidecars are quite rare as far as I've seen. Also, the leader pattern is mostly used by databases so we might anyways end up using them.
Thanks Akos!
That's a great breakdown, Saurabh! And thank you for the mention, friend!
Thanks Petar