Sharding Postgres with Basic tier in Hyperscale (Citus), how why and when

#1

Post by onderkalaci » Sat, Apr 17, 2021, 4:59 PM UTC

Sharding Postgres with Basic tier in Hyperscale (Citus), how why and when
techcommunity.microsoft.com

Re: Sharding Postgres with Basic tier in Hyperscale (Citus), how why and when

#2

Post by I_am_tiberius » Sun, Apr 18, 2021, 4:27 PM UTC

Is it difficult to migrate an existing database to Citus? In my project I designed the database so that each table includes a tenantId - so in this regard I'm well prepared I guess.

Re: Sharding Postgres with Basic tier in Hyperscale (Citus), how why and when

#3

Post by onderkalaci » Mon, Apr 19, 2021, 6:57 AM UTC

I_am_tiberius wrote: post #2

Is it difficult to migrate an existing database to Citus? In my project I designed the database so that each table includes a tenantId - so in this regard I'm well prepared I guess.

As far as I can tell, considering that you are planning to migrate a multi-tenant application, you are pretty much ready to go. One step you should be careful is to make sure that all your queries include the tenantId filter.

There is a step-by-step documentation for migrating multi-tenant apps to Citus, which might help you to decide how much ready you are for a migration: https://docs.citusdata.com/en/latest/develop/migration.html#...

(p.s. I'm the author of the post)