News for hackers. Stuff that matters.
Re:How we built scalable spatial indexing in CockroachDB by orthecreedence on Monday December 14, 2020 @08:41PM (#25426018)
Ehh, if they were posting stupid marketing content, yeah I agree. But they are posting mostly technical articles that are very informative and interesting if you follow the DB (which I do, loosely, and almost used it in production but another DB ended up winning out).

I like seeing stuff like this and I don't view it as promotion (or if it is, it's 10% promotion and 90% technical content).

Re:How we built scalable spatial indexing in CockroachDB by forquestions on Tuesday December 15, 2020 @08:18AM (#25429992)
Out of curiosity, which other DB ended up winning out?
Re:How we built scalable spatial indexing in CockroachDB by orthecreedence on Tuesday December 15, 2020 @01:00PM (#25432907)
ScyllaDB. I was replacing a high-write Postgres instance (10% creations, 90% updates), and was testing out a drop-in replacement that could "just scale." CRDB did wonderfully, but ultimately I decided to rearchitect the problem to fit more of a CRDT model (albeit a crappy version) and just throw an endless stream of events at the DB which get reconstructed when the data is pulled out.

The model ended up working fantastically well, and I can't say enough about how much I like ScyllaDB so far. I will say I wish there was an easier backup method, but I understand that's a big ask on a distributed DB and automating our backups wasn't that difficult.