However we have a whole team working to improve Postgres and we always prefer to contribute those efforts to the Postgres community.

Vitess today is not the Vitess of 2021. About 70% of the current codebase was written in the last five years, based on lessons we learned running it at scale.

Neki is built for Postgres from the ground up, by the engineers who did that work.

On the Multigres comparison, I'll admit we get a bit salty, mostly because "Vitess for Postgres" invites the comparison. But to date there's no public evidence of a working sharding implementation in Multigres. Their sharding design doc landed this week, and it lists cross-shard query planning and resharding execution as explicitly out of scope.

Neki does sharding today, including online resharding that switches traffic without a maintenance window. It isn't open source, but you can spin up a cluster and try it yourself.

https://planetscale.com/blog/postgres-18-is-now-available

https://github.com/vitessio/vitess/graphs/contributors?from=...

  ls -lh hello.wasm
  -rw-r--r--@ 1 tcole  staff    24M Apr 22 14:18 hello.wasm

  cat hello.py
  print("Hello, Wasm!")

  time python3 ./hello.py
  Hello, Wasm!

  ________________________________________________________
  Executed in   26.86 millis    fish           external
     usr time   16.37 millis    0.13 millis   16.24 millis
     sys time    7.25 millis    1.14 millis    6.11 millis

  time wasmer hello.wasm
  Hello, Wasm!

  ________________________________________________________
  Executed in   84.77 millis    fish           external
     usr time   50.26 millis    0.14 millis   50.12 millis
     sys time   28.97 millis    1.21 millis   27.76 millis

  time wasmtime hello.wasm
  Hello, Wasm!

  ________________________________________________________
  Executed in  141.72 millis    fish           external
     usr time  120.86 millis    0.13 millis  120.72 millis
     sys time   16.65 millis    1.20 millis   15.45 millis

I think you're suggesting they might have a canary fleet, but there wasn't anything/enough that preventing a mistake from bypassing the carry fleet before going to production?

Could be!

When I first got the Volvo the GPS and LTE connection would periodically stop working for a day or two. They pushed a fix for it. Later they added CarPlay, which wasn't there when I got the car. Good updates. But not as frequent at Rivian.

Was Volvo able to fix it with another OTA or did people have to go in for service?

I got my R1T in June 2023 and since here are a few things they've improved, just off the top of my head, not bothering to look it up:

1. Significant improvement to ride quality via different / better suspension tuning.

2. Ability to schedule warming the cabin and pre-condition the battery

3. Completely redesigned the UX for setting drive modes and suspension height (for the better IMO)

4. Added a ton of car info, like battery temp, motor temp, and other info like altitude, various angles the vehicle is at (for off-roading), degrees the front wheels are turned

5. Added additional settings for ride softness / firmness (I got this update yesterday and haven't tried it yet)

When an update is ready I get a notification in the car and from the Rivian app on my phone. I can just hit apply and it installs it.

IMO a USB install would be a substantially worse experience and it would be much less likely that customers would actually install it.

But, for the type of person who just wants the car to stay the same as it was the day they bought it, and never change, it's not the vehicle for them. Personally I really like that it's continually improving and I don't have to go in for service or even go out to the truck to do an update.