.NET Modernisation

The compatibility of the existing application or rearchitecting on .NET Core

your current .Net architecture, framework, codebase and dependencies. Output is a compatibility report together with a suggested roadmap.
may have different paths based on the output of the initial step which makes an analysis on possible scenarios and also time cost-complexity of this is estimated
and handover of the final state internally together with applying a enriched CI/CD pipeline

.NET Reloading

.NET Programming language is adapting itself to the changes in the software industry. One of the major changes is cross-platform support: .NET can be built and run on Linux-based Operating Systems, which brings cost savings and the option to run .NET on Kubernetes. Moreover, after open-sourcing .NET, there is increasing community support for .NET with its lightweight architecture that brings higher performance compared to the previous .NET versions. .NETCore is now the preferred version for all new projects. For legacy applications, there is a refactoring/porting effort needed for .NETCore.


Modernisation Paths

.NET framework has been evolving for many years and each framework version has its own structure. Based on the current framework version, there are several alternate paths as described in the diagram.




Screenshot 2020-02-12 at 11.55.37


Cost Saving: Various options together with Serverless, managed resources, auto-scaling(Even scaling to 0!), zeroing Windows OS and SQL Licenses

Performance: Moving away from IIS means getting away from various overheads together with .NETCore’s lightweight and lean architecture which boosts performance

Cloud-Native: Kubernetes-driven infrastructure, together with Cloud functions which brings self-healing and automation on your development and deployment cycles

Cross-Platform: Possibility to run your workload on both Windows and Linux and even on Kubernetes!

Get in touch