I'm not sure how well an account per microservice would work in practice for larger projects, at least without a "staging" account.
Part of the point of microservices to me is if one is needed, spin that sucker up. Having to go to IT to get a new account and billing set up is some serious friction to that.
This is where automating the account creation is needed. Yes if you are in an organization where going over to IT is your method of provisioning accounts, that could be painful. However, I would argue that is not efficient and would encourage that organization to think about allowing teams to own the entire infrastructure of their systems. This includes provisioning accounts.
This, of course, spins into another conversation that is much larger than what this post covers. Certainly, there is a vast amount of things to consider if your organization is needing to make that kind of change.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not sure how well an account per microservice would work in practice for larger projects, at least without a "staging" account.
Part of the point of microservices to me is if one is needed, spin that sucker up. Having to go to IT to get a new account and billing set up is some serious friction to that.
This is where automating the account creation is needed. Yes if you are in an organization where going over to IT is your method of provisioning accounts, that could be painful. However, I would argue that is not efficient and would encourage that organization to think about allowing teams to own the entire infrastructure of their systems. This includes provisioning accounts.
This, of course, spins into another conversation that is much larger than what this post covers. Certainly, there is a vast amount of things to consider if your organization is needing to make that kind of change.