Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • I think this is fairly subjective. It depends on many factors other than size, and whether it's "worth it" is entirely up to you. Commented Nov 14, 2019 at 21:17
  • Docker has a different use case than microservices. Commented Nov 14, 2019 at 21:27
  • And to be fair, your application doesn't look like it's large enough to benefit from microservices. Microservices are the new golden hammer (where everything looks like a nail), but realistically I don't see the benefits unless you're large and/or geographically dispersed. Commented Nov 14, 2019 at 21:29
  • 1
    Fair enough. Frankly, I think you'd benefit more by gradually moving your application to ASP.NET MVC. You'd get a significant performance improvement, and your application would become modular enough where working with microservices would become a more viable option. Commented Nov 14, 2019 at 21:31
  • 1
    OK, so there are plenty of resources on the Internet that say why one might to choose a Microservices architecture, but I'm a big fan of balancing those advantages with the potential costs, so here is an article that sheds some light one what some of those costs are: blog.runscope.com/posts/5-reasons-not-to-use-microservices Commented Nov 14, 2019 at 21:45