Scale apps Using Node.js Microservices on Heroku | Modern App Development on Salesforce

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

Hi there,

Do you think its a good idea to have auth service, account service in a microservices or just one of them responsible for login, logout, register, delete account, forgot password etc etc

at the moment I have two service, auth and account

account is responsible for adding user and other user profile features.
the auth is only responsible for issuing token when the user tries to request. so it only has one function at the moment

but thinking about this, I realised that I am over doing things, I could include anything to do with user in one service and thats it instead of having account service talking to auth service about a new user added.

do you get my point ?

what is your input on this ?

do you think its a good idea to have auth service and account service or the account service alone should be enough and later I can create a service that will responsible for controlling users settings as an example.

so basically what I mean, I should have one service called "account service" and that service is responsible for adding user, login, logout etc etc just like in a monolith app or two services, one responsible for generating token and checking if users is banned, not verified.

so for example, if I ban a user, I only need to switch that isBanned to true from the auth.

well I could do the same in account service.

what do you think a good option to have or both are valid
thanks

chihabahmed
Автор

I want scenario based interview questions

naganaga
Автор

Shouldn't SalesForce give some kudos / money / crypto / coffee to the creator of **jsForce**? C'mon Marc Benioff, don't be so...

barabimbaraboom