Distributed Microservices Solution with Azure Service Fabric
Question
You develop an entertainment application where users can buy and trade virtual real estate. The application must scale to support thousands of users.
The current architecture includes five Azure virtual machines (VM) that connect to an Azure SQL Database for account information and Azure Table Storage for backend services. A user interacts with these components in the cloud at any given time.
-> Routing Service "" Routes a request to the appropriate service and must not persist data across sessions.
-> Account Service "" Stores and manages all account information and authentication and requires data to persist across sessions
-> User Service "" Stores and manages all user information and requires data to persist across sessions.
-> Housing Network Service "" Stores and manages the current real-estate economy and requires data to persist across sessions.
-> Trade Service "" Stores and manages virtual trade between accounts and requires data to persist across sessions.
Due to volatile user traffic, a microservices solution is selected for scale agility.
You need to migrate to a distributed microservices solution on Azure Service Fabric.
Solution: Create a Service Fabric Cluster with a stateful Reliable Service for each component.
Does the solution meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B
The proposed solution of creating a Service Fabric Cluster with a stateful Reliable Service for each component appears to meet the requirements of migrating to a distributed microservices solution on Azure Service Fabric.
Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices and containers. It provides the infrastructure to build highly available, scalable, and self-healing microservices-based applications.
Stateful Reliable Services in Service Fabric allow for the creation of services that maintain state across sessions. These services can store data in local storage or external storage such as Azure Storage, Azure SQL Database, or Cosmos DB. Stateful services are better suited for scenarios where data persistence is required.
In the given scenario, the Routing Service should not persist data across sessions, while the Account Service, User Service, Housing Network Service, and Trade Service all require data persistence across sessions. Therefore, creating a stateful Reliable Service for each of these components should allow for the required data persistence.
By leveraging Service Fabric for the microservices solution, the application can scale and handle volatile user traffic by distributing and load-balancing services across multiple nodes. Service Fabric also provides monitoring and management capabilities to ensure the application stays highly available and responsive.
Therefore, the proposed solution of creating a Service Fabric Cluster with a stateful Reliable Service for each component meets the goal of migrating to a distributed microservices solution on Azure Service Fabric. Therefore, the correct answer is A. Yes.
