AWS Microservice Extractor for .NET simplifies the process of refactoring older monolithic applications into smaller code projects to build a microservices-based architecture. Modernize and transform your applications with an assistive tool that analyzes source code and runtime metrics to create a visual representation of your application and its dependencies. You can also extract the codebase into separate projects that teams can develop, build, and operate independently to improve agility, uptime, and scalability.
AWS Microservice Extractor for .NET uses source code analysis and runtime metrics to produce a visualization that shows dependency graphs, runtime metrics (for example, runtime call counts), and static references between code artifacts (for example, classes). You can use the visualization and call counts to understand dependencies between components and identify the heavily called ones. Additionally, Microservice Extractor for .NET provides you with alternate visualization for grouping based on namespaces and islands.
With automated recommendations, developers get guided experience to refactor legacy applications. Microservice Extractor now identifies common extraction candidates using heuristics-based techniques, and highlights those in visualization. These recommendations can be used as is or used as a starting point to extract microservices off of monolithic codebase. Thus, automated recommendations from Microservice Extractor helps to speed up refactoring large applications even if the developer is unfamiliar with the codebase.
After manually removing dependencies to prepare parts of the application for extraction (shown as “islands” in the visualization), you can use Microservice Extractor for .NET to extract API endpoints. Microservice Extractor for .NET carves out the code that underlies these API endpoints by replacing local calls with network calls. You may then develop, build, and deploy these projects as you see fit. AWS recommends that you thoroughly test your application after transforming it with Microservice Extractor for .NET before using it in production.