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: Deploy a Windows container to Azure Service Fabric for each component.
Does the solution meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
The proposed solution to deploy a Windows container to Azure Service Fabric for each component does meet the goal of migrating to a distributed microservices solution on Azure Service Fabric.
Azure Service Fabric is a distributed systems platform that simplifies the deployment, management, and scaling of microservices-based applications. It provides a flexible and scalable infrastructure for building and deploying microservices, allowing for easy scaling based on demand.
By deploying each component as a separate container in Azure Service Fabric, the solution meets the requirements for a microservices architecture. Each container can be scaled independently of the others based on the specific needs of that component, which allows for better resource utilization and cost optimization.
Furthermore, using containers provides a consistent deployment and runtime environment for the microservices, which simplifies management and reduces the risk of compatibility issues.
In terms of the specific requirements for each component, the proposed solution can accommodate them. The Routing Service does not require data to persist across sessions, and the other services - Account Service, User Service, Housing Network Service, and Trade Service - require data to persist across sessions, which can be achieved by storing the data in Azure SQL Database or Azure Table Storage.
Overall, the proposed solution of deploying a Windows container to Azure Service Fabric for each component meets the requirements for a microservices architecture and provides the necessary scalability and agility for the entertainment application to support thousands of users. Therefore, the answer is A. Yes.