authentication server microservice, should I use different services for different user functionalities

Question

I have an authentication server using oauth2.

I use it for :

1. Authentication from the other services, subscription, change and retrieve password etc.

2. As resource server to store and retrieve more users and groups informations. I have a ManyToMany relationship between users and groups.

Should I seperate the second part of functionalities of this app on another standalone service that will work as resource server only. And only keep the authentication part on the authorization server?

That way I could horizontally scale these two services separately.

Answer 1

Yes, the better idea would be to have the configuration as a separate standalone service running on cloud. With configuration server as a separate service you can add all the authorization and other sort of details like DB details, API details, messaging queue configuration etc, and get connected to N number of services.