You probably don't want microservices, just small, normal, sane, "context bound" services. Microservices come at a huge cost if done well. Just watch a talk fr

You probably don't want microservices, just small, normal, sane, "context bound" services. Microservices come at a huge cost if done well. Just watch a talk from netflix/uber/... method calls become remote requests, so you need fallback strategies, log tracing, service discovery, circuit breaking, ... As long as you can do merges on your codebase without horrible problems, you almost certainly don't need microservices. Splitting a huge laravel/symfony/cakephp app into a few smaller ones, that is probably a good idea, and you don't need any particular tooling to do it.