Skip to main content

Azure Service Fabric: Understanding Microservices

Source: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-overview 
Microsoft Azure Service Fabric helps developers build applications based on microservices to allow better scalability, faster deployment and upgrades, reduced resource costs and enhanced management capabilities.

Microservices is the latest stage of the trend to divide applications into component parts.  This trend leads to separation of the user interface, business logic, storage and other elements that make up an application.  It has been manifest in shared libraries and technology layers, and created greater mobility and scalability of applications.

A monolithic approach to application development contains all its functionality and is typically scaled by adding more instances of physical or virtual services.

Source: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-overview-microservices

Microservices take this logic much further.  They ideally are autonomous and interact with each other through well defined protocols.  Microservices may be developed in many programming languages and run in many environments, but they are compatible with each other because of standard communications protocols.  When a microservice fails, a resilient microservice will restart on the same or another environment, and will not break the overall performance of the application even as upgrades are applied and maintenance is performed.

Service Fabric can run on premises as well as in the cloud, and it may include clusters with other cloud providers. It provides the overall framework for deploying microservices and orchestrating upgrades and maintenance of services.

Microsoft uses Service Fabric for many of its services, such as Azure SQL Database, Azure Cosmos DB, Cortana, Microsoft Power BI, Microsoft Intune, Azure Event Hubs, Azure IoT Hub, Dynamics 365, Skype for Business, and many core Azure services.

The most popular competitors to Azure Service Fabric are Kubernetes (a Linux container management tool from Google), Docker Swarm, and Microsoft's own Azure Container instances for managing Docker containers.


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan