Comparison
MicroservicevsService layer
Microservice
the service you own deploys on its own schedule and you have never waited for another team's release.
A service small enough to be owned, deployed and reasoned about by one team independently of the others. The unit of value is independent deployment, not size — a service that cannot be released without coordinating is not buying you anything. The price is real and permanent: every in-process call you replaced is now a network call that can be slow, partial or absent, and every debugging session now spans machines.
Full entry →Service layer
there is one method per use case, it opens the transaction, calls the model, and contains no business rules itself.
A boundary layer defining an application's operations as a set of use-case methods, coordinating transactions, security and the domain objects that do the work. It is what keeps controllers thin and what gives an application an API independent of its user interface. It is also the layer that quietly absorbs domain logic until the model beneath it is anaemic, which is the failure to watch for.
Full entry →