5 ms·
You could consider one of these three – 1. yugabytedb (postgres compatible) 2. cockroachdb (postgres compatible) 3. tidb (mysql compatible) You could self-h
by vinay_ys 4y ago
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).
- sgtfrankieboy 4y agoIt's also a real option with CockroachDB, unless you need regional sharding. Which a lot don't actually need anyways.
- rad_gruchalski 4y agoYugabyteDB tablespaces will get you there inside of their Apache 2 license.
- 411111111111111 4y agoIt 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.
- anecdotal1 4y ago[dead]
- alexvoda 4y agoI 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.
- rad_gruchalski 4y agoYugabyteDB supports triggers. YugabyteDB is not just „postgres compatble”, it is postgres with a distributed layer.