Description
Move the auth server from Keycloak to Zitadel.
The reason for this sudden change is because Keycloak does not fundamentally align with the idea behind this repository. Keycloak was originally designed for creating and securing applications that were dealing with ONE TENANT. However this went bust when we implemented Multi-tenancy which is an issue since Keycloak requires memory and ability to deal with more tenants.
One way to achieve this was to use Realms create a multi-tenant architecture however Realms too have a memory limit and can cause issues with maintainability. Yet another problem is with Adaptors, true that Keycloak exposes a REST API however creating Realms with the exposed REST API seems to be problematic when using anything except JAVA which enforces ADMIN API to be exclusively be written in JAVA.
Changes required
- Switch from Keycloak to Zitadel as authentication server
- Switch the Authentication server's Database Management System from Postgres to CockroachDB, enables better horizontal scaling compared to Postgres (Cockroach DB is friends with Postgres)
Description
Move the auth server from Keycloak to Zitadel.
The reason for this sudden change is because Keycloak does not fundamentally align with the idea behind this repository. Keycloak was originally designed for creating and securing applications that were dealing with ONE TENANT. However this went bust when we implemented Multi-tenancy which is an issue since Keycloak requires memory and ability to deal with more tenants.
One way to achieve this was to use
Realmscreate a multi-tenant architecture however Realms too have a memory limit and can cause issues with maintainability. Yet another problem is with Adaptors, true that Keycloak exposes a REST API however creatingRealmswith the exposed REST API seems to be problematic when using anything except JAVA which enforces ADMIN API to be exclusively be written in JAVA.Changes required