|
You are here |
compositecode.blog | ||
| | | | |
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. | |
| | | | |
alexdebrie.com
|
|
| | | | | In this post, understand the different concepts of consistency as applied to distributed databases, as well as some issues with the conversation of consistency. | |
| | | | |
ravendb.net
|
|
| | | | | RavenDB and MongoDB evolved to support ACID transactions at the cluster level, debunking the myth that NoSQL databases can't be ACID-compliant. Learn more. | |
| | | | |
michaelscodingspot.com
|
|
| | | Michael Shpilt's Blog on .NET software development, C#, performance, debugging, and programming productivity | ||