Explore >> Select a destination
|
You are here 
|
www.allthingsdistributed.com | ||
| | | | |
henrikwarne.com
|
|
| | | | | What a great book Designing Data-Intensive Applications is! It covers databases and distributed systems in clear language, great detail and without any fluff. I particularly like that the author Martin Kleppmann knows the theory very well, but also seems to have a lot of practical experience of the types of systems he describes. There is... | |
| | | | |
jeffreytse.net
|
|
| | | | | System design is the process of defining the architecture, interfaces, and data for a system that satisfies specific business requirements. A good system design requires engineers to think about everything in an infrastructure, from the hardware/software, down to the data and how it's stored. | |
| | | | |
timilearning.com
|
|
| | | | | My notes from the fifth chapter of Martin Kleppmann's book: Designing Data Intensive Applications. | |
| | | | |
timilearning.com
|
|
| | | One common pattern in the previous systems we have discussed like MapReduce, GFS, and VMware FT is that they all rely on a single entity to make the key decisions. While this has the advantage of making it easier for the system to decide, the downside of this approach is that the entity is now a single point of failure. In this post, we'll learn how the Raft consensus algorithm solves this problem. | ||
