|
You are here |
cedardb.com | ||
| | | | |
ayende.com
|
|
| | | | | The Uber Engineering group have posted a really great blog post about their move from Postgres to MySQL. I mean that quite literally, it is a pleasure to rea... | |
| | | | |
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. | |
| | | | |
blog.canoozie.net
|
|
| | | | | A write-ahead log (WAL) is one of those database concepts that sounds deceptively simple. You write a record to disk before applying it to your in-memory state. If you crash, you replay the log and recover. Done. Except your disk is lying to you. PostgreSQL, SQLite, RocksDB, Cassandra... every production | |
| | | | |
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 ... | ||