[HN Gopher] Announcing Vitess 11
___________________________________________________________________
Announcing Vitess 11
Author : ksec
Score : 59 points
Date : 2021-07-29 16:43 UTC (6 hours ago)
(HTM) web link (vitess.io)
(TXT) w3m dump (vitess.io)
| studmuffin650 wrote:
| Just need something like this for postgres and we would jump on
| it. Citus is close, but all the features that are important are
| behind their exceptionally tall paywall.
| samlambert wrote:
| We are seeing a bunch of folks moving away from Postgres over
| to MySQL + Vitess for this reason. Including a major website
| that we will be able to talk about soon.
| btown wrote:
| For their hosted system, it's not particularly worse than
| hosted Postgres on RDS. RDS costs $0.50/hr for a 4 core/32GB
| db.r5.xlarge. Azure-hosted Citus for multi-node workloads on a
| similarly sized node are $0.618/node/hr. Both double in price
| to have a high availability backup cluster.
|
| https://aws.amazon.com/rds/postgresql/pricing/
|
| https://azure.microsoft.com/en-us/pricing/details/postgresql...
|
| Of course, the answer is that both are insane markups. But it's
| worth being able to focus on other things!
| pm90 wrote:
| GCP Product Managers, here's an idea that will rain you with
| cash: managed vitess to replace the severely underpowered
| cloudsql offering.
| ericyan wrote:
| Or even better, something like PlanetScale [1]. It was founded
| by the maintainers of Vitess.
|
| [1]: https://www.planetscale.com/
| js4ever wrote:
| Unfortunately their infrastructure is only in the US, so
| latency is a deal breaker from Europe
| raitom wrote:
| This is cool. Exactly the product I wanted for hosting my
| side projects without paying the exorbitant price for a MySQL
| instance on AWS or GCP.
| dkhenry wrote:
| A few things I am really excited about in this release are the
| new protbuf compiler ( https://vitess.io/blog/2021-06-03-a-new-
| protobuf-generator-f... ) and the improvement on end to end speed
| ( https://benchmark.vitess.io/macrobench?ltag=10.0.0&rtag=11.0...
| )
|
| Vitess was already one of the most performant distributed
| databases, this is really pushing the limits even further.
| NovaX wrote:
| The last version, 10, brought in a scan resistant cache (the PR
| is interesting [1]). It would have made a fun blog post.
| Hopefully they can write more about the internals when they
| make these types of improvements.
|
| [1]
| https://github.com/vitessio/vitess/pull/7439#issuecomment-77...
| nimrody wrote:
| Is Vitess still used by Youtube or did they eventually move to
| one of Google's internal planet-scale databases?
| ericyan wrote:
| I heard that YouTube has migrated to Spanner already. YT was
| the last major user of MySQL at Google, the Googlers probably
| consider that as a snowflake and wanted to move away from it.
| Nothing wrong with Vitess itself.
| tiffanyh wrote:
| So what's the goto replication software to use for MySQL or
| Postgres these days?
| porsager wrote:
| I would definitely say pg-auto-failover[1]. It's the only one
| that doesn't have a ton of moving parts, and it helps you get a
| good base setup too at the same time.
|
| [1]: https://github.com/citusdata/pg_auto_failover
| tiffanyh wrote:
| I completely missed the news that Microsoft acquired Citrus
| back in 2019.
|
| I noticed in their MIT like license it referred to Microsoft
| and was confused until I learned they were acquired.
|
| https://github.com/citusdata/pg_auto_failover/blob/master/LI.
| ..
| ericyan wrote:
| If you use Oracle MySQL or Percona Server, I would recommend to
| try group replication[1], no third-party software required.
|
| MariaDB can use something similar called Galera Cluster.
| Percona also has its own version, called Percona XtraCluster
| (PXC).
|
| For more traditional MySQL/MariaDB replication typologies,
| Orchestrator[2] is a great tool.
|
| For postgres, I have heard a lot of good words about
| Patroni[3], although I never used it myself.
|
| [1]: https://dev.mysql.com/doc/refman/8.0/en/group-
| replication.ht...
|
| [2]: https://github.com/openark/orchestrator
|
| [3]: https://github.com/zalando/patroni
| hu3 wrote:
| Hi! I'm interested in scaling MariaDb with active-active
| replicas. They call it ring replication:
| https://mariadb.com/kb/en/replication-overview/
|
| I would appreciate any comments. Specially on the upsides and
| downsides.
| ericyan wrote:
| That's a footgun.
|
| For ring replication to work, it requires all replication
| sources (aka. "masters") to be online at all times. This
| never happens in real life, so it is just a matter of time
| that you get a nasty split-brain. Star replication tries to
| mitigate this by a crazy setup with replication filters
| that is painful to maintain and probably will break after
| some DDL statements.
|
| Moreover, neither of these can handle conflicts. If a row
| gets updated on different hosts at the same time, you will
| get broken replication and/or split-brain.
|
| To scale writes, sharding is usually the way to go and
| Vitess can be handy for that. By the way, MySQL group
| replication has multi-primary mode that is safer. Galera
| Cluster/PXC probably has something similar but I am not
| completely sure.
| samlambert wrote:
| This.
| teach wrote:
| Vitess is "a database clustering system for horizontal scaling of
| MySQL."
|
| Come on, folks. Never put out a press release without a simple
| description about what your thing even is.
| ksec wrote:
| May be I should have included it in the title. ( But HN also
| has a rule for title not being edited ).
|
| It is too late now, HN was down for about an hour and it is now
| outside the editing window. And while I do agree there should
| be a description on the front page of any project ( I am
| usually the one one rant about it ), I dont think such
| description is necessary in every changelog or release note.
| teraflop wrote:
| It's not a press release, it's a blog post targeted at people
| who use the software.
| teach wrote:
| And yet it was posted on Hacker News, where presumably most
| of the visitors do not use it.
| tshaddox wrote:
| And yet it received enough votes to be on the front page,
| meaning enough visitors were aware of it or interested
| enough to spend 5 seconds investigating what it is!
| kevinmgranger wrote:
| Is the submitter the author of the blog post?
| sergiotapia wrote:
| planetscaledb uses vitess under the scenes
| moralestapia wrote:
| I hope they improved their service though. The promise is great
| but last time I tried them it was a very slow and buggy
| experience.
| samlambert wrote:
| Hey, I am sorry you had a bad experience on the platform. We
| released as a beta and have made rapid improvements. I am
| confident if you give us another try you will have a better
| experience.
|
| If you have feedback or want to chat feel free to email me:
| sam@planetscale.com
| js4ever wrote:
| Hey Sam I checked Planetscale few weeks ago, it seems
| incredibly promising ... But having it only in the US is a
| deal breaker from Europe
| samlambert wrote:
| We have an EU region launching within weeks. Thank you
| for checking us out and hanging in there.
| ksec wrote:
| It definitely need a FAQ somewhere, from Backup, Uptime
| Guarantee, to where are the Server / DC located, etc.
___________________________________________________________________
(page generated 2021-07-29 23:00 UTC)