I do a lot of writing and speaking on microservices (writing a book for The Pragmatic Bookshelf on the topic). I don't think that authorization and/or authentication are good candidates to be split into services. The reason is that every other portion of your system will need to communicate with them in real time, which breaks the key feature of what makes something a service--autonomy. It introduces temporal coupling and isn't any different than a standard monolith, only now it's distributed, and you have to deal with HTTP calls between components.
I gave a talk once that kind of introduces some of these ideas, and it might be useful to you: https://www.youtube.com/watch?v=h8ihxzfqH0A. It's a deep topic, and if you watch that talk and want to go over more questions, I'm happy to help more. On Friday, May 25, 2018 at 5:15:10 PM UTC-6, vivek poddar wrote: > > Hi, > > I am writing an micro service which aims to solve the issue of > authenticating > and authorising users on different client applications. > > I am new to micro services but its still in early phase of development. I > would > like to hear some feedback as well as architectural advice from the > community. > > Thanks, > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/8668ed7b-b639-41d6-8a64-e97167feb618%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
