6 ms·
They probably use MySQL for Basecamp and it's worked for them so they're also using it for Hey (same team developing both). As for Vitess it makes sense since i
by dmlittle 6y ago
They probably use MySQL for Basecamp and it's worked for them so they're also using it for Hey (same team developing both). As for Vitess it makes sense since it's made to work nice with Kubernetes (which they are using). I don't know of a Postgres equivalent.
- mr_ndrsn 6y agoding ding ding We have a winner!
- ksec 6y agoIs there a Vitess for Postgres?
- dmlittle 6y agoLooking at Vitess' roadmap[1] it's in their medium term roadmap but I'm not aware of any other project that currently support Postgres. [1] https://vitess.io/docs/resources/roadmap/ https://vitess.io/docs/resources/roadmap/
- sougou 6y agoThis is still in our plans. We're likely to launch by end of year.
- Sammi 6y agoIsn't Citus sort of the same? https://www.citusdata.com/ https://www.citusdata.com/
- ksec 6y agoYes but I feel Vitess is much more widely used than Citus. MySQL community, last time I check has formed a more mature ecosystem and conscious on HA and Clustering. Postgres still feels more like throwing you a bunch of options and you are on your own. It is not that a solution being more widely used means it is good, you are just less likely running into edge cases with no help at all.