Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You could consider one of these three –

1. yugabytedb (postgres compatible)

2. cockroachdb (postgres compatible)

3. tidb (mysql compatible)

You could self-host these on azure or subscribe to each of their managed service offering.

Of course, sticker price for managed will be more expensive than self-hosted enterprise product which itself will be more expensive than the self-hosted, community-supported, open-source option (which seems to be a real option with YugabyteDB).



It always triggers me to read "postgres compatible" when they've entirely skipped features such as database triggers

They've just selected a few features from postgres which they're compatible in.


I agree. I guess what they mean is you can use the existing adapter for your language.

The PostgreSQL organisation should create some trademarked badges to properly label the levels of compatibility other products offer.


YugabyteDB supports triggers. YugabyteDB is not just „postgres compatble”, it is postgres with a distributed layer.


It's also a real option with CockroachDB, unless you need regional sharding. Which a lot don't actually need anyways.


YugabyteDB tablespaces will get you there inside of their Apache 2 license.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: