Explore >> Select a destination
|
You are here 
|
reubenbond.github.io | ||
| | | | |
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. | |
| | | | |
my-it-notes.com
|
|
| | | | | Databases - how they work under the hood?Key takeaways from brilliant book "Designing data intensive application" - to quickly recap core concepts. DB engines classifications Type of load: OLTP (transaction processing) vs OLAP (data warehousing and analytics) Relational vs NoSQL, document vs columnar, graph vs triple-store (semantic facts storage) Even within NoSQL camp you can ... | |
| | | | |
decomposition.al
|
|
| | | | | by Devashish Purandare ยท edited by Sohum Banerjea and Lindsey Kuper | |
| | | | |
speakerdeck.com
|
|
| | | An introduction to Raft and its implementation in java, Barge. | ||
