I really like the way Uncle Bob described Microservices in this article: https://blog.cleancoder.com/uncle-bob/2014/10/01/CleanMicroserviceArchitecture.html htt

I really like the way Uncle Bob described Microservices in this article: https://blog.cleancoder.com/uncle-bob/2014/10/01/CleanMicroserviceArchitecture.html https://blog.cleancoder.com/uncle-bob/2014/10/01/CleanMicros... He made the point that micro-services are a deployment method not an architecture. A good clean architecture shouldn't care how it's deployed. If you need to move from plugins to micro-services to be massively scalable your architecture shouldn't care. If you need to move from micro-services to plugins to make your app simple to host and debug, your architecture should also not care. This strategy has been implemented in frameworks like abp.io very successfully. You can start your application as a single collection of split assemblies deployed as a single application and move to deploying as micro-services when it's necessary.