You have been tasked with planning the migration of your company's application from on-premises to Google Cloud. Your company's monolithic application is an ecommerce website. The application will be migrated to microservices deployed on Google Cloud in stages. The majority of your company's revenue is generated through online sales, so it is important to minimize risk during the migration. You need to prioritize features and select the first functionality to migrate. What should you do?
When planning the initial migration of a company's monolithic ecommerce application to microservices in Google Cloud, it is crucial to minimize risk and ensure the stability of core revenue-generating processes. The product catalog, having integrations only to the frontend and product database, represents a relatively independent and foundational component of the website. Migrating it first keeps disruptions minimal, allows validation of the migration process, and lays a solid groundwork for subsequent migrations of more complex functionalities. Starting with this less critical yet significant feature helps gain experience with the new infrastructure with lower risk.
I agree with Option A, as the question states “first one”
Yes, I vote A
https://cloud.google.com/architecture/migrating-a-monolithic-app-to-microservices-gke#example_migrating_a_shopping_cart Answer A
I don't agree with option A. Google docs says: "When you plan your migration, it's tempting to start with features that are trivial to migrate. This might represent a quick win, but might not be the best learning experience for your team. Instead of going straight to the migration, you should spend time evaluating all of the features and create plans for their migration." "According to this evaluation framework, the ideal candidate for the initial migration effort should be challenging enough to be meaningful, but simple enough to minimize the risk of failure. The initial migration process should also: Require little refactoring, considering both the feature itself and the related business processes. Be stateless—that is, have no external data requirements. Have few or no dependencies." I think it's between options B & C since the third-party vendors already have a microservices architecture going on. https://cloud.google.com/architecture/migrating-a-monolithic-app-to-microservices-gke#:~:text=When%20you%20plan,for%20their%20migration.
as it says in your link: A migration plan example The following list shows an example of a migration order: Platform frontend; that is, the user interface Stateless features, such as a currency-conversion service Features with independent datasets (datasets that have no dependencies on other datasets), such as a service to list your brick-and-mortar stores Features with shared datasets—the business logic of the ecommerce platform so the first one should be the user interface = product catalogue
A is correct
I will vote C. It is the only service where a temporary disruption will not impact all sales on the website (because it is not embedded in the frontend).
Agree Option A , in order to keep the disruption as minimum as possible by migrating minimum features
Minimal Risk: Migrating the product catalog first minimizes risk because it's a foundational component of your ecommerce website. It doesn't directly impact the core revenue-generating processes like payment or order fulfillment. Independent Functionality: The product catalog is relatively independent, with integrations primarily to the frontend and product database. This makes it easier to isolate and migrate without disrupting other critical parts of the application. Early Validation: Migrating the product catalog allows you to validate your migration process, test your infrastructure, and gain experience with Google Cloud before moving on to more complex functionalities. Foundation for Future Migrations: A successful product catalog migration sets the stage for future migrations of more complex features. It provides a solid foundation for building out your microservices architecture on Google Cloud.
I will go with A as it has less dependencies.
A should be the first MVP item in the list. Key is to avoid risks in the initial stages of transition.
https://cloud.google.com/architecture/migrating-a-monolithic-app-to-microservices-gke#example_migrating_a_shopping_cart Based on the guide referenced, the answer would be D. Migrate the Shopping cart, which has integrations to the frontend, cart database, inventory system, and payment processing system. The guide recommends migrating functionality with the least dependencies and level of complexity first, which the shopping cart functionality has fewer dependencies and less complexity than the other options presented. This will minimize risk while still providing value to the business and allowing further migration of more complex functionality.
Migrating the product catalog first may be a good option if the product catalog is a separate service that doesn't rely on other services and can be deployed independently. However, if it is closely tied to other services such as the frontend or product database, migrating it first may introduce complexity and increase the risk of the migration, as the other dependent services would need to be migrated or integrated with the new product catalog service in parallel.
A is the answer. https://cloud.google.com/architecture/migrating-a-monolithic-app-to-microservices-gke#choosing_an_initial_migration_effort
A is correct.