#Different Service
1 messages · Page 1 of 1 (latest)
Hi @coarse night, as you described we only have service and not libraby since we're providing an central authorization solution that you can use among your applications and services at scale. Would you be against a call to discuss how exactly do you want to position and use Permify ?
I'm looking at implementing monolith architecture where everything is done in one application instead of multiple services, so permission stuff should also be done in the same codebase. Having too many microservices adds unnecessary complexity.
If necessary, I don't mind a call to discuss this
Got it, with monolith you can use Permify as sidecar if you like. But again it won't behave as library again its still service.