A development team is converting a legacy monolithic system into a container-based microservices solution with newly introduced frameworks. This transition calls for major structural changes to the application’s code. Which approach addresses this type of transformation best?
Adapt the system to a new platform with moderate design updates
Migrate the system to a new environment while preserving the existing code base
Upgrade the system in stages while keeping foundational components intact
Reengineer the system’s code and architecture to implement a new design
By reengineering the system’s code and architecture, the large-scale reshaping necessary for the new container-based microservices model takes place. Preserving the existing code base or making moderate changes to the design does not address the application's need for a substantial restructure. Incrementally upgrading the system while keeping most existing components intact still falls short of the sweeping changes required to accommodate new frameworks and containers.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What exactly does reengineering a system’s code and architecture involve?
Open an interactive chat with Bash
What are the key benefits of using a microservices architecture over a monolithic system?
Open an interactive chat with Bash
Why are containers particularly well-suited for microservices?