/explore
|
You are here 
|
emptysqua.re | ||
| | | | |
xdg.me
If you're reading this blog, it's a good bet that sometime in your life you've had a computer freeze or crash on you. You know that crashes happen. If it's your laptop, you restart and hope for the best. When it's your database, things are a bit more complicated. Historically, a database lived on a single machine. Writes are considered "committed" when they are written to a journal file and flushed to disk. Until then, they are "dirty". If the database crashes, only the committed changes are recovered from disk. |
|
| | | | | ||
| | | | |
www.debugbear.com
Server-side rendering ensures that website content appears quickly, without first having to download and run application code. |
|
| | | | | ||
| | | | |
curatedsql.com
[AI summary] A collection of technical articles covering SQL Server TLS 1.2 migration, high availability architecture, PowerShell testing, and connecting Power BI to Azure HDInsight. |
|
| | | | | ||
| | | | |
maheshba.bitbucket.io
There are three questions to ask of any system: What abstraction does it implement? What is the design space for such an abstraction? Why is this abstraction useful? In a previous post, we examined the Paxos protocol and answered the first two questions. Paxos implements the abstraction of a Write-once Register (a WOR) using a combination of quorums and a two-phase locking protocol. As for the third question: Paxos is useful because it can be used to implement MultiPaxos (among other things). But that's an unhelpful answer unless you know what MultiPaxos does. In this post, we seek to understand MultiPaxos by asking the same three questions of it. To start with, what abstraction does MultiPaxos implement? MultiPaxos implements State Machine Replication. Cons... |
|
| | | |||
