gh-ost VS duckduckgo-locales

I’ve been through multiple incidents where everything worked fine in the testing environment but ended up locking the production database for minutes when deployed. A category of open-source tools called OSC (Online Schema Change) exists to mitigate such pain, like gh-ost used by GitHub and OSC used by Meta. They work by creating a set of "ghost tables" to apply the migrations, copy over old data from the original tables, and catch up with new writes simultaneously. When all old data is migrated, you can trigger a cutover to make the "ghost tables" production. Check the post below for a great introduction and comparison:

Sounds like it's basically explained in the gh-ost readme https://github.com/github/gh-ost#how

I think it amounts to "use views to decouple access to the table with a fixed interface" and "use triggers for migrating data between tables"

Gh-ost is the new hotness. Simple to use and lots of great features: https://github.com/github/gh-ost

As they have said it depends on the size of the table on disk and the number of rows, but an alter in production is not difficult to last from seconds to days. I don't know if you are doing the alter as is but try to check https://docs.percona.com/percona-toolkit/pt-online-schema-change.html or https://github.com/github/gh-ost , they usually simplify a lot the alters.

Not sure which version of MySQL you're using, but one approach would be to use a tool like pt-online-schema-change (from Percona) or g-host -- which will create a duplicate table and then swap it in place of the original table. It's a safer approach when operating in production environments. Here's a good comparison of the tools many people use https://planetscale.com/docs/learn/online-schema-change-tools-comparison

Actually I never tried but I was scared by the small print of GH not using RDS themselves [1] and Ghost relying on lower-level features that might be not easily available in RDS. Also I had the impression you have to setup a normal non-RDS replica attached to your RDS master?

[1] https://github.com/github/gh-ost/blob/master/doc/rds.md

MySQL has some robust tooling in this space. Some of the tools use triggers to copy to a new table. GitHub's gh-ost[1] is probably the state of the art, and uses the binary log stream to replicate the data.

[1] https://github.com/github/gh-ost

https://github.com/github/gh-ost/issues/331#issuecomment-266...) it does become a little bit of a "you do not have google problems" type discussion.

(Perhaps you do have such problems, I don't know where you work! But 99%+ of companies don't have such problems and never will.)

GitHub doesn't use foreign keys[1], and there's likely many tables related to all the users, notifications, permissions, etc... that would need to be cleaned up. Without foreign keys they likely have some system process that does this instead of a simple `DELETE FROM` which cascades.

1. https://github.com/github/gh-ost/issues/331#issuecomment-266...

By magic I mean the complexity brought on by the heavy use of metaclasses, patterns employed via convention rather than enforced by code (implying that you have to read enough of the code before you understand the patterns) and other similar leaky abstractions.

Don't get me wrong, I do think Django is one of those deep modules[1] where the interface makes it a pleasure to work with but the internals do need effort. Especially the ORM layer.

[1] https://duckduckgo.com/?q=deep+modules+John+Ousterhout&t=fpa...

https://duckduckgo.com/?t=ftsa&q=mfsbsd ?

There have been others in the past, but this seems to be the most polished and ready to use ATM(for FBSD).

Another would be NanoBSD (also FBSD).

For NetBSD you're on your own, starting from there https://wiki.netbsd.org/tutorials/how_to_create_bootable_net... , and/or asking on https://daemonforums.org/ , https://www.unitedbsd.com/ (taking inspiration from some 'live-distro' discussed there. like 'OS-108'), reddit(?), 'crap-overflow', and even https://www.linuxquestions.org/.

Of course you're free to use the official NetBSD mailing lists, and some obscure IRC-channels in even more obscure IRC-networks also :-)

(You won't be spoon-fed, and are expected to have read the manuals and other documentations...)

A good alternative to writing your own echo server and debugging requests one route at a time is requestbin, which will gladly take any requests you throw at it, log them, and optionally return a response of your choice.

Lots of different implementations and hosts: https://duckduckgo.com/?q=requestbin

Take a look at these pictures:

https://duckduckgo.com/?q=cluttered+old+persons+home&atb=v31...

I was thinking that people who live in an environment like this are most in need of a robot to help them.

Not to be snarky, but UPS fires are one of the leading causes of datacenter fires: https://duckduckgo.com/?hps=1&q=UPS+Fire+datacenter&ia=web