From my point of view, Microsoft has done a great job of running several platforms lately. It all started when they released the .Net platform code.
It seems like once again they are investing in various platforms, this time in the cloud! They provide a new framework called Service Fabric that can be deployed for any type of cloud (as I understand it).
This is practically everything I know about Service Fabric. Can you explain more clearly what it's for?
What is it?
Service Fabric is a distributed systems platform that facilitates packaging , deployment and management of scalable and reliable micro-services. It addresses the significant challenges of developing and managing cloud applications. Empowering developers and administrators to avoid complex infrastructure problems and focusing on deploying critical and demanding workloads knowing they are scalable, reliable, and manageable.
What's the use?
Service Fabric allows you to create and manage scalable, reliable applications made up of microservices running at a very high density in a shared pool of computers (known as a cluster). It provides a sophisticated runtime for creating distributed, scalable, stateless and stateless microservices. It also provides comprehensive application management capabilities for provisioning, deploying, monitoring, updating / patching, and deleting deployed applications.You can create Service Fabric clusters in many environments, including Azure or on-premises, on Windows Server, or on Linux. In addition, the development environment in the SDK is identical to the production environment, with no emulators involved. In other words, if it runs in the local development cluster, it will be deployed to the same cluster in other environments.
Key Features
These are the key features listed in the Service Fabric Overview . :
- Develop massively scalable applications that are self-recovering.
- Develop applications made up of microservices using the Service Fabric programming model. Or, simply executable host guest and other application structures of your choice, such as ASP.NET Core 1 or Node.js.
- Develop micro-services with and without highly reliable state monitoring.
- Simplify your application design by using stateful monitoring services instead of caches and queues.
- Deploy to Azure or local clouds running Windows Server or Linux without any code changes. Write once in any place and deploy to any Service Fabric cluster.
- Develop using a "data center" approach on your computer. The local development environment uses the same code that runs in Azure data centers.
- Deploy applications in seconds.
- Deploy applications at a higher density than virtual machines, deploying hundreds or thousands of applications per computer.
- Deploy different versions of the same application side by side, each independently upgradeable.
- Manage the life cycle of your applications with no downtime, including immediate or non-immediate updates.
- Manage applications using .NET, PowerShell, or REST interfaces.
- Update my services and apply patches to them within applications independently.
- Monitor and diagnose the health of your applications and set policies to perform automatic repairs.
- Climb the Service Fabric cluster vertically or horizontally with ease, knowing that the applications are scaled according to the available resources.
- Observe the self-healing feature balancer administer the redistribution of applications in the cluster. Service Fabric recovers from faults and optimizes the distribution of load distribution based on available resources.
Reference:
