How to convert MVC.NET application in to microservice

Question

0.00/5 (No votes)

See more:

I have a mvc application structure like below

Web
Web.Business
Web.Database
Web.Domain
Web.Tests

Now I want to convert it to micro service

What I have tried:

As I am very new to micro service I don't know where to start

Posted 29-Mar-20 18:40pm

Mohammad Nawaz

Updated 29-Mar-20 21:43pm

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2020-03-29T21:32:00

Solution 1

.NET Microservices. Architecture for Containerized .NET Applications | Microsoft Docs[^]

Posted 29-Mar-20 21:32pm

Richard MacCutchan

Afzaal Ahmad Zeeshan · Answer 2 · 2020-03-29T21:44:00

Quote:
I want to convert it to micro service

You need to focus on a domain-driven analysis of your application to be able to successfully migrate a monolith to a microservice. Normal distribution of the applications happens at different levels, as we distribute the front-end and back-end first.

Among these two ends, you then distribute the code based on:

Complexity of the code
Performance bottleneck/degradation
Separation of concerns
Maintain availability for solution

You keep separating different components of your application into modules and smaller processes that make it easier to manage the development and deployment.

Think of it this way, if a module can be developed alone, tested alone, deployed and function alone, it is a microservice. More advanced questions include, if it can be scaled alone, it can be made fault-tolerant alone, then it is a separate module.

Oh, and the tech stack should also be microservice level. You should focus on making your modules available via Docker or other container runtimes. That will give you control over how your applications scale.

Here are a few good resources, How to break a Monolith into Microservices[^]
Migrating to Microservices from a Monolithic App[^]