Because we blogged about our new vectorized sql engine[1] & our new parallel commit protocol[2] recently, two "big"-ish engineering lifts that were packed into this one release.
Probably has to do with their decision to name it after the cockroach. I mean, if they had called it MaggotDB or BotFlyDB or TapewormDB, people might find it unappealing.
You can't even kill it with Boring Company's flamethrower! Tardigrades are virtually indestructible as going into space and coming back won't always kill them.
Comments
CockroachDB seems to be getting a lot of attention and marketing cycles lately... What has made it the focus of late?
Because we blogged about our new vectorized sql engine[1] & our new parallel commit protocol[2] recently, two "big"-ish engineering lifts that were packed into this one release.
[1]: https://www.cockroachlabs.com/blog/how-we-built-a-vectorized...
[2]: https://www.cockroachlabs.com/blog/parallel-commits
It has a lot of promise to provide Spanner-like functionality to people outside of Google.
Marketing
Probably has to do with their decision to name it after the cockroach. I mean, if they had called it MaggotDB or BotFlyDB or TapewormDB, people might find it unappealing.
Those aren't nearly as resilient though. Now, if you made a version of sqlite that replicated itself inside your program then you could use botfly ...
The successor will have to be named TardigradeDB.
You can't even kill it with Boring Company's flamethrower! Tardigrades are virtually indestructible as going into space and coming back won't always kill them.