Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
yugabyte-db
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
Uff... Let's go give a look at the licenses: https://github.com/cockroachdb/cockroach/blob/master/LICENSE
So many licenses, including the Business Source License which is non-free license.
Also there's this CockroachDB Community License (CCL), which I guess is a made-up license that's going to include some whatever terms.
I might still accept this mix of licenses however I can't find the definition of "foundational features" -- what do I "lose" by using the OSS version instead of one of their managed offerings?
From a quick overview, it's soft-no from me (in the sense that it probably wouldn't be my first choice).
Shameless plug: check out [Rosettable https://github.com/francoisp/rosettable]. Brings Postgres triggers and notifies to your MySQL schema, with it you can organize a smooth transition. Using MySQL_fdw you can use your current MySQL schema with the above you can know when a client interacted directly with MySQL; all the while you add some nice jsonb and Plpgsql and transition out of MySQL incrementally. Don’t rewrite, write onward
Online schema change solutions have been around for over the past decade and are commonly used to ALTER TABLE with no downtime (or with minimal interruption) on the largest deployments of MySQL today.
The two most common solutions are pt-online-schema-change and gh-ost, and if you are running MySQL today and still running direct ALTER TABLE suffering outage, then you're in for a pleasant change.
On top of that, most MySQL ALTER TABLE operations with InnoDB tables support non-blocking, lockless operation as well. My main concern with these is that they're still replicated sequentially leading to replication lags.
MySQL is also slowly adding "Instant DDL", currently still limited to just a few types of changes.
Disclosure: I authored gh-ost (at GitHub), oak-online-alter-table (the original schema change tool) and am a maintainer for Vitess and working on online schema changes in Vitess.
Links:
- https://www.percona.com/doc/percona-toolkit/3.0/pt-online-sc...
- https://github.com/github/gh-ost
- Past HN discussion: https://news.ycombinator.com/item?id=16982986
- https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-op...
- https://vitess.io/docs/user-guides/schema-changes/
as we are all discussing the pros and cons of various DBs, my favourite MySQL feature has to be the pluggable storage engines. Being able to support both InnoDB and RocksDB backed tables in the same database is wonderful. Just today I made use of the MyRocks storage engine's handy TTL [1] feature instead of a tedious delete & optimise scheduled job
[1]https://github.com/facebook/mysql-5.6/wiki/Time-to-Live-%28T...
That’s good to know!
If the first result is not reputable, that’s still a smell (but a different kind of smell) for MySQL. https://duckduckgo.com/?q=innodb+vs+myisam
