2 ms·
Perhaps the focus should be on how people interact with the services. If everyone interacts with the login service through the same interfaces, then they don't
by Jtsummers 10y ago
Perhaps the focus should be on how people interact with the services.
If everyone interacts with the login service through the same interfaces, then they don't need to know how it breaks out internally or care.
If, however, you use it through one set of API features, and I use it through another very disconnected set, then perhaps it's time to break it down further.
At the end of the day, though, what does it contain? A list of users, their roles, and access control mechanisms. Does it make sense to have unified logins or multiple sets of logins across your company's services? If the latter, break it down to be run once per other application with specialised selection of features per application. If the former, let the login team handle control of the system and leave it a 100k monolith or break it down as they see fit.