According to Microsoft, Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable Microservices and addresses the significant challenges in developing and managing cloud applications. Service Fabric is basically thinking in the form of Microservices and putting them in the cloud. Thinking about the Monolithic concept of services which is basically decomposing the services into smaller services to do a specific task. It has its own challenges as well stating dealing with more infrastructure and management of multiple instances of services instead.
The intent of Azure Service Fabric is to extend developers with an indeed rich proclamation that addresses large amount of the complexities that are originally associated by the whole of building cloud-based distributed applications
It’s one of the service that’s the backbone of the most Microsoft Products:
- Azure Core
- Skype For Business
- Azure SQL
- Azure Document DB
- Service Bus
- Power BI
- Event Hubs
Service Fabric can be individually deployed, updated, distributed, and scaled. These smaller units are run in containers rather than directly on VMs. Service Fabric can handle the management and scaling of these containers, with potentially hundreds of containerized Microservices running on a single VM.
The main reasons behind the usability of the Service Fabric are:-
- They enable you to scale different parts of your application depending on its needs
- Development teams are accomplished to be preferably flying in rolling inaccurate changes and thereby provide features to your customers faster and more frequently
- It supports creating both stateless and stateful Microservices – an architectural approach where complex applications are composed of small, independently versioned services – to power the virtually complex, low-latency, data-intensive scenarios and scale them into the cloud.
- Provides the benefits of orchestration and automation for Microservices by all of new levels of app depth of perception and insight.
- Solves hard distributed systems problems adore state management and provides application lifecycle management capabilities so developers don’t feel responsible for re-architect their applications as usage grows.
- Includes Visual Studio tooling as well as command line support, which enables developers to quickly and easily build, test, debug, deploy and update their Service Fabric applications on single-box deployments, demonstrate deployments and production deployments.
Service Fabric Programming Models
Service Fabric offers two high-level frameworks for building services. Although both of these programming frameworks are built on the same Service Fabric core, they are targeted to solve different kinds of service problems. These two frameworks are:
- Reliable Actors APIs:Actors are similar to .NET objects as they encapsulate not only state but also their behaviors. Each of these Actors can interact asynchronously in a request-response pattern with other Actors or services.
- Reliable Services APIs:Traditionally or in the WCF world, services demand external systems (out of process) for valid state management. Service Fabric gives us Reliable Collections, which is similar to C# generic collections to store state along by all of the service in the same manner (co-location). This reliable state gets replicated to all told the replicas in various nodes to provide valuable reliability and availability with reduced latency. A pluggable communication model makes it ultimately more powerful to manage out of the box listeners or incorporate a custom communication listener to support any kinds of transport protocols: HTTP, TCP, and so on.
Basically when we install service fabric on the Windows Server We get nothing but Azure Stack
Service Fabric is a platform-as-a-service framework from Azure to build hyper-scale, highly reliable, and easily-managed applications for the cloud. It addresses many of the significant challenges in developing and managing cloud applications.