Migration to v2 platform architecture

[thebengeu]

In our previous platform architecture, our Storage, Realtime, and connection pooler (PgBouncer) services were bundled together, with a single instance of each service per project.

For our v2 architecture, we’ve “unbundled” these services, moving to a multi-tenant model, where a single instance of each service serves many projects:

This frees up as much resources as possible for your Postgres databases, while enabling us to offer more resource intensive features for these services, and opens the door to capabilities such as zero-downtime scaling.

With Supavisor replacing PgBouncer, along with some other key optimizations, the final pieces of our v2 architecture are now ready.

Paid plan rollout (completed)

We’ve already fully rolled out our v2 architecture to paid plan projects. You now have more resources available, for the same price that you’ve been paying.

Free plan gradual rollout (20 March 2024 onwards)

• 20 March 2024: Newly created or unpaused projects will use v2 architecture
• 28 March 2024: Existing projects will start being migrated to v2 architecture

This will be a gradual rollout - we will email you at least one week before your project is scheduled to be migrated.

Your action for projects scheduled to be migrated

For newly created or unpaused projects on the Free Plan, no action is required.

For existing projects on the Free Plan, up to a few minutes of downtime is expected for the migration. For each of your projects, we’ll identify the 30-minute maintenance window where your project had the least database queries over the previous 10 weeks.

You have two choices:

• Automatic Migration: If you don't take any action, we plan to do the migration automatically during that maintenance window with the least historical activity.
• Manual Migration: Any time before that, you can go to Project Settings > General to see whether/when the maintenance window is scheduled (timings will also be included in the email). There, you may choose to manually restart the project yourself, at a time that is convenient for you. Your project will be restarted on v2 architecture.

[ImSingee]

Curiously: I'm on paid plan and havn't experienced any downtime. But you point out that free plan projects will have several minutes downtime. Is there any archetecture difference between free and paid plan projects?

[thebengeu]

Yes, there may be architecture differences between free and paid plan projects, due to differing resource constraints, extra features offered, uptime SLAs, etc. Such architecture changes are also subject to changes.

[mkmoisen]

How do we upgrade our local development environments to use the new v2 architecture?

[thebengeu]

The v2 architecture changes are mainly relevant for the Supabase hosted platform. Since so many projects are hosted there, moving to a multi-tenant model, where a single instance of each service serves many projects, is a significant optimization.

Conversely, each local development environment serves a single project, so using a similar multi-tenant architecture as on the Supabase hosted platform would add complexity, such as additional databases and API calls needed to store tenant information, which aren't necessary for the single-tenant case.

[mshamia]

Is the change only on platform architecture, with no change related to the code?

[thebengeu]

Yes, purely architectural, doesn't involve any code changes from our users.

[ShJavokhir]

This Migration wasn't succesfull on my project and causing problem in production