A pretty good article and I am looking at Yugabyte more seriously (again).
But I still have questions:
1. Is CockroachDB actually faster (generally) than Yugabyte? Their (own) benchmarks seem to show it is.
2. If true, why? Did writing their own pgsql-compat interpreter really make that much of a difference?
3. This is the big one for me: why does Yugabyte have such large percentages of code in its Github repo in different languages, especially Java, JS and TS? I expect to see a small amount of scripting languages like Python for building or testing or whatever, but it appears that around 30% of the code is actually Java, for a server that was built on top of pure Postgresql. (I'm not a fan of Java in general, except for Elixir.)
Other than those questions, Yugabyte looks like a pretty good migration target and their licensing approach is refreshing.
But I still have questions:
1. Is CockroachDB actually faster (generally) than Yugabyte? Their (own) benchmarks seem to show it is.
2. If true, why? Did writing their own pgsql-compat interpreter really make that much of a difference?
3. This is the big one for me: why does Yugabyte have such large percentages of code in its Github repo in different languages, especially Java, JS and TS? I expect to see a small amount of scripting languages like Python for building or testing or whatever, but it appears that around 30% of the code is actually Java, for a server that was built on top of pure Postgresql. (I'm not a fan of Java in general, except for Elixir.)
Other than those questions, Yugabyte looks like a pretty good migration target and their licensing approach is refreshing.