Hello, We are planning to move our application from zero to abp.
Us company have multiple saas projects
To use apb effectively, i try to create empty moduler projects & architectural
My main purpose, if we want us projects have to work modular monolith(unified on one host) or seprated(like mikroservice at firstly them will be like macroservice)
For authentication & authorization if customer use all products, projects have to use one single sign on server, or if we want we have to seprate auth for each project
For each project i created 2 solution, firstly with application template Company.ProjectName (host for main module) and with module template Company.ProjectName.MainModule (it could be contain more small services/modules in feature)
If we want unified them, i will create one host solution and will referance each ProjectName.MainModule
My main question is if we use single authentication & authorization server, how will we manage create user & permissions, i guess each project have to user table because each project have different props for users. For example if project a want to create user, are we create it firstly project a and sync to identity or opposite? For permissions management, each project will have too many permissions, should we control them from a single point? can every project manage own permissions? I mean should auth server know all permissions for each project?
1 Answer(s)
-
0
See https://docs.abp.io/en/abp/latest/Microservice-Architecture
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
