Your company has developed a monolithic, 3-tier application to allow external users to upload and share files.
The solution cannot be easily enhanced and lacks reliability.
The development team would like to re-architect the application to adopt microservices and a fully managed service approach, but they need to convince their leadership that the effort is worthwhile.
Which advantage(s) should they highlight to leadership?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
The best answer to the question is C, as it highlights several advantages of adopting microservices and a fully managed service approach to re-architect the application. Here are the detailed explanations for each of the advantages mentioned in option C:
Easier to decouple infrastructure from application: In a monolithic application, the code is tightly coupled, making it difficult to make changes to one part without affecting others. Microservices, on the other hand, are designed to be loosely coupled, with each service having its own codebase, data storage, and interface. This allows for more flexibility and easier updates to the application, without impacting the entire system.
Develop and release new features: Microservices are designed to be modular, which means that each service can be developed and tested independently, without affecting other parts of the system. This makes it easier to add new features or fix issues without requiring a complete system overhaul.
Manage underlying infrastructure: With microservices, the infrastructure can be managed independently of the application. This means that updates and maintenance can be performed on each service without impacting the entire system. Additionally, microservices can be deployed on a range of infrastructure options, including fully managed services like Kubernetes or AWS ECS, providing even more flexibility.
Manage CI/CD pipelines and perform A/B testing: Microservices can be integrated into a DevOps workflow, making it easier to manage continuous integration and continuous deployment pipelines. Additionally, with a microservices architecture, it's easier to perform A/B testing, allowing developers to test new features or changes without affecting the entire user base.
Scale the solution if necessary: Microservices are designed to be scalable, with each service able to scale independently of the others. This allows for more efficient use of resources, as only the services that require additional capacity need to be scaled.
Option A is incorrect because while a fully managed service approach can help reduce costs and make it easier to manage infrastructure, it doesn't necessarily automatically manage CI/CD pipelines.
Option B is incorrect because converting the monolithic application to a container with Docker is just one step in the process of re-architecting the application to a microservices architecture. It doesn't highlight the full range of benefits that come with adopting a microservices approach.
Option D is incorrect because Migrate for Compute Engine is a tool used to migrate virtual machines to Google Cloud Platform, and doesn't address the benefits of adopting a microservices architecture.