UUID migration for Active-Active (multi master) DB replication

[netmaxt3r]

Hello, I am trying to achieve true active-active replication. I am using postgres spock extension at database level.

I am problems with syncing sequences. spock recommended postgress extension snoflake to generate node specific sequence id generation instantly breaks new user account creation, probably due to snowflakes large sequence numbers.

so far i am running with node offset sequence as a work around.

So i thought of migration authentik models to UUID based primary key. most of the sequences are from M2M relations and few from auto generated pk

• tables are from django core auth apps can be ignored since they are not used ( roles and groups are handled by authentik models
• django meta data tables (like django_content_type,django_migrations) can also be ignored since we cannot modify them, also sync issue can be avoided by using one node as pseudo master node to do all django related operations such as authentik upgrade
• M2M sequences can be avoided by routing through custom through models ( i have working poc migration for some models )
• Some model tables still uses id number as primary key ( eg;- authentik_core_user, authentik_core_groupsourceconnection etc).

I do see some work has been done in many models to uuid.I dont know know why some are still using number based . I any one have more knowledge on previous migration discussion please let me know.

this require a significant number of django migration , before i dive in to the rabbit hole, any guidance or advice would be greatly appreciated.
Thanks