Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Share logic for caching users per service #15

Open
marinasundstrom opened this issue Apr 2, 2024 · 0 comments
Open

Share logic for caching users per service #15

marinasundstrom opened this issue Apr 2, 2024 · 0 comments

Comments

@marinasundstrom
Copy link
Owner

Each service might want to locally cache users and organizations so to easily retrieve the information when needed.

Today you need to implement this manually for each service.

Background

Identity Manager publishes events when a tenant, user, or organization, has been created, updated, or deleted.

It is up to each service to consume to those events, and to create their own locally cached representation of users and so.

Adding that functionality for a service is quite tedious today. You need to create Entities for at least Users, Organizations, OrganizationUsers, and perhaps for keeping track of permissions/claims.

You might also need to define new repositories, and commands. Copying is not even a great idea when logic is diverging. You get the point.

Objective

We should investigate how to share as much code as possible without sacrificing the flexibility for each service.

Similar to the Domain.* projects in Common.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment