Migrate monolith into service fabric

Christian Havel 1 Reputation point


we have a .NET 4.7 monolith and think about to "put this into" Azure Service Fabric.

We are Azure Service Fabric newbies. Do I understand it correctly, that we can put our existing monolith into a Service Fabric and deliver a setup to the customer, that contains the binaries from our setup and a a Service Fabric Runtime?

What is the path to put an existing project into a Service Fabric?

We think that the Service Fabric, I call it a environment, that will make us fit for the future to split our monolith into microservices. The split into microservices should help us to achive high availability and scalability.

Best Regards,

Azure Service Fabric
Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
258 questions
{count} votes

1 answer

Sort by: Most helpful
  1. jakaruna-MSFT 596 Reputation points Microsoft Employee

    You can technically ship your monolith application in service fabric. But that will come with some challenges.

    In service fabric, Stateful apps is recommended to run at least 3 replicas. So its immune to a node failure. But we can run only one replica of our monolith app. During updates, Services can move from one node to another.
    If we have once replica, We will have a downtime which we dont need.

    Resource allocation may be a problem if your monolith app needs more resources(cpu and memory) than a single node has. This will become a problem when it moves from one node to another.

    If you are fine with the above constraints, Then you can try out the deployment.

    Refactoring monolith into smaller apps will be the correct option. But that will take some time.

    This document under service fabric discusses about converting a monolith app into microservices.

    0 comments No comments