Vercel Service Markup

Re:Vercel Service Markup by nikita on Wednesday May 03, 2023 @01:47AM (#35798476)

Agree on the callout. This one we are going to enable soon so it's fixable. So the correction is that it's architecturally possible, but temporarily disabled. Hope we will be able to run Supabase on it soon!

Also there are some storage plugins that won't work b/c we take over Postgres low level storage.

[ Parent | on HN ]

Re:Vercel Service Markup by harshitgangal on Wednesday May 03, 2023 @01:53AM (#35798513)

Likewise in Vitess. It is architecturally possible to add 100% compatibility :)

[ Parent | on HN ]

Re:Vercel Service Markup by nikita on Wednesday May 03, 2023 @02:42AM (#35798874)

Well it’s much much harder. Query plans over the distributed system should be different and transaction coordination is different when queries span shards.

It’s impossible to give 100% performance compatibility.

[ Parent | on HN ]

Re:Vercel Service Markup by shlomi-noach on Wednesday May 03, 2023 @02:54AM (#35798972)

Vitess maintainer here. I feel like the discussion was about 100% feature (queries/protocol/...) compatibility and that somehow it shifted to 100% performance compatibility? 100% performance compatibility is trivially not something to claim.

[ Parent | on HN ]