Source: dzone.com
Microservice, Miniservice, and MacroserviceCategory: Database
by Every organization is trying to decompose its application/product and convert into Microservices, so that they can sell their product in name of Micro-Services based architecture.
You can call your service as Micro-Service if and only if it is: So, if your service is not following any of this principle, then it is not a Microservice, and you may be working on Mini-service, which I will explain shortly.
You can call your service as Miniservice if: Now, if all your service domain services share a single database and application server and call each service through direct calls, as they all are deployed in the same JVM, then your application is a Monolith (Macroservice).
Teams and developers are decentralizing their application as much as they can, however not writing as many Microservices as you might think.
You can call your service as Micro-Service if and only if it is: So, if your service is not following any of this principle, then it is not a Microservice, and you may be working on Mini-service, which I will explain shortly.
You can call your service as Miniservice if: Now, if all your service domain services share a single database and application server and call each service through direct calls, as they all are deployed in the same JVM, then your application is a Monolith (Macroservice).
Teams and developers are decentralizing their application as much as they can, however not writing as many Microservices as you might think.
Related Articles
Community Partners
DevOps Careers