shlomi-noach

8 ms·

31.
by shlomi-noach 5y ago
There is always a schema, and PlanetScale, in particular, promotes the use of schemas. That is, behind the scenes we operate Vitess, which is an infrastructure and sharding framework on top of MySQL. You will create schemas in PlanetScale
32.
by shlomi-noach 5y ago
Per https://news.ycombinator.com/item?id=27203568 , there is a a normal MySQL schema. This is about how PlanetScale solves the schema management friction, so as to enable developers working with schemas: safe branching, on
33.
by shlomi-noach 6y ago
Deepthi, tech lead for Vitess, just published this RFC a few days ago: https://github.com/vitessio/vitess/issues/7084 Vitess plans to support PostgreSQL, but there is no work on that at this time.
34.
by shlomi-noach 8y ago
The origin of the name 'freno' is discussed in the README: https://github.com/github/freno#whats-in-a-name What's in a name? "Freno" is Spanish for "brake", as in car brake.
35.
by shlomi-noach 8y ago
Asterix: "You make me sick talking about boars" Obelix: "And you bore me talking about sickles" (inexact quote from memory, Asterix and the Golden Sickle) Absolutely priceless translation!
36.
by shlomi-noach 8y ago
They can be a hassle when you want to shard your data, having outgrown your single-instance capacity. You will either shard functionally (extracting complete tables to other database servers), in which case FKs will completely break, or hor
37.
by shlomi-noach 8y ago
No, on the database itself. I used "child side" for lack of better terminology. Every foreign key has two edges: the "parent" table and the "child" table. Rows in the "child" table depend on existence
38.
by shlomi-noach 8y ago
Author of gh-ost here. Actually, it should be possible to support child-side foreign keys. They would have to be named differently (the foreign key constraint has a unique name in a schema) -- but it should work. See discussion in https:&#
39.
by shlomi-noach 8y ago
Author of gh-ost here. Here are my thoughts on migrating to a different RDBMS: http://code.openark.org/blog/mysql/mysql-vs-postgresql-gh-os...
40.
by shlomi-noach 9y ago
Since you already use HAProxy you should get that almost for free. Your app would talk to the databased by communicating through HAProxy, which would direct traffic to the single-writer; HAProxy's health tests would detect who the sing
41.
by shlomi-noach 9y ago
> In my experience, real-world concurrency issues (that you are talking about) are always hard to find in manual/automated testing I agree, and I don't have a good, generic, strategy for that. I didn't give the best exampl
42.
by shlomi-noach 9y ago
Agreed, and having some experience with both MySQL and SQLite, running SQLite in testing cannot cover problems you'd find with MySQL (e.g. SQLite is so limited with concurrency that you cannot use it to confirm concurrency issues will
43.
by shlomi-noach 9y ago
I'm curious whether pretix attempted using MariaDB/Galera with single-write mode, such that the three servers still run synchronous replication, but only one of them gets the writes. I suspect (disclaimer: not running Galera mysel
44.
by shlomi-noach 9y ago
Here's how to see all your PRs: https://github.com/search?q=is:pr+author:YOURNAME&type=Issue... Here's how to see all your open PRs: https://github.com/search?q=is:pr+is:open+author:YOURNAME&am
45.
by shlomi-noach 9y ago
> I'd be willing to bet over 99.999% of all deployed production web applications serving requests today -- has a bottleneck at the database and the network that dwarfs any overhead from language performance A language is not just ab
46.
by shlomi-noach 9y ago
Just curious about the MySQL problems you hit. MySQL replicas self-recover via MASTER_CONNECT_RETRY and MASTER_RETRY_COUNT. e.g. set to 1, 8640000 respectively to make a replica retry every one second for up to 100 days before finally givin
47.
by shlomi-noach 9y ago
> MariaDB 10 was a game changer for the mysql landscape Can you please elaborate in what respect?
48.
by shlomi-noach 9y ago
> I've been looking for something similar for Postgres and MySQL/MariaDB without any luck, and it really surprises me there's not more interest in doing migrations this way. skeema (suggested above by evanelias) and square
49.
by shlomi-noach 9y ago
@jivid the logical backups are done per-table, not per-server. Per-table logical backups are useful to the engineers owning the data. It makes it easy for them to restore data from a single table. When an engineer loads logical backup data
50.
by shlomi-noach 11y ago
Enough with the FUD please. These claims are so 80s. MySQL & InnoDB is fully ACID compliant.