I told my boss that for our next application, we will be creating rest services that follows the microservices architecture. The design I had was somewhat like this:
all functions related to users - 1 rest service all functions related to payment - 1 rest service all functions related to audit log - 1 rest service all functions related to corporate accounts - 1 rest service etc..etc..
Problem is he didn't agree with that. He mentioned somewhat like a microservice must contain finer functions. Something like one microservice for this particular type of payment, another for another payment type, one of user creation, one for user details, etc. He says my design shouldnt be called a microservice design architecture.
So my question is...does my design really follow the microservice design principle? it is too coarse grained and should be finer? is my boss right? what is the maximum limit of the finer detail functions a microservice should have?
I need your help. Would appreciate anyone who could shed light on this. Thank you