Really depends on your domain, but reading up on &quot;bounded contexts&quot; and &quot;domain-driven design&quot; will help you in determining which microservices might be named and designed in your area. For example in online retail, seperate microservices for Customers, Products (catalog), Product reviews and Orders might be a feasible distribution of responsibility, functionality and data.<p>Note that there&#x27;s always a catch in going from a monolithic application to one with a more distributed nature. Distribution of data requires data synchronization and results in integration challenges, because of the unreliability and higher latency of networks.<p>Lastly, Martin Fowler c.s. wrote some nice articles on microservices: <a href="http:&#x2F;&#x2F;martinfowler.com&#x2F;tags&#x2F;microservices.html" rel="nofollow">http:&#x2F;&#x2F;martinfowler.com&#x2F;tags&#x2F;microservices.html</a>. That will help as well.