This guide describes how to migrate .NET applications from a monolithic architecture to a microservices architecture. It covers the pros and cons of monolithic and microservices architectures, and how to evaluate whether you need to migrate. The guide also describes how to implement the migration, including how to split the monolithic application, how to communicate between microservices, and how to test and deploy microservices.
This guide covers considerations for refactoring a monolithic ASP.NET application into a microservice-based architecture. It addresses the process of modernizing legacy applications to extend to cloud-based services, aiming to reduce technical debt and improve scalability and security. The document focuses on moving from .NET Framework to the cross-platform .NET version on Linux.
This guide covers considerations for refactoring a monolithic ASP.NET application into a microservice-based architecture.
Modernization is the process of progressively transforming existing applications and infrastructure to extend to higher-value, cloud-based services.
DraftKings, CoStar, and AgriDigital are mentioned as planning to move their applications to the cloud by refactoring them to use the cross-platform version of .NET.
A monolithic application is one in which all functionality lives in one source repository, and is deployed as a single unit.