[英]authentication server microservice, should I use different services for different user functionalities
I have an authentication server using oauth2.我有一个使用 oauth2 的身份验证服务器。
I use it for:我将它用于:
Authentication from the other services, subscription, change and retrieve password etc.来自其他服务的认证、订阅、更改和找回密码等。
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.这样我就可以分别水平扩展这两个服务。
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.
使用配置服务器作为单独的服务,您可以添加所有授权和其他类型的详细信息,例如 DB 详细信息、API 详细信息、消息队列配置等,并连接到 N 个服务。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.