|
You are here |
planetscale.com | ||
| | | | |
cnr.sh
|
|
| | | | | I've been talking to some of the folks at Data Mountaineer about their new Cassandra CDC connector for Kafka connect, and I wanted to record some of the nuances that developers should consider ... | |
| | | | |
vitess.io
|
|
| | | | | An in-depth technical discussion on the limitations of foreign keys in MySQL and why the can't play nicely with online DDL | |
| | | | |
antzucaro.com
|
|
| | | | | The Scenario Let's suppose you are modeling a database in MySQL 5.5. Based on your knowledge of the requirements for the application behind this database you can guess which of the tables within it are going to be huge. For those huge tables you want to plan ahead to make sure that you can scale out your data such that you have less headaches in the future. Here's the catch: you want to keep it simple until it comes time to scale out. | |
| | | | |
boringsql.com
|
|
| | | Two concurrent sessions, same page, different answers. An interactive tour of xmin, xmax, snapshots, and the visibility rules that decide what PostgreSQL lets you see. | ||