Financial implications of migrating legacy systems to Cloud-native architectures – Part 1

This article will be split into a multi-part series.

There is a gathering trend for many legacy applications to be migrated to a ‘Cloud native’ architecture. While, some are being migrated for cost reasons, others are for scalability reasons.

What is a typical legacy architecture?

This is one based on technologies such as Java or .Net stack and include a user interface, backend, middleware and database, designed for traditional hardware-based devices.

What is a Cloud-native architecture?

It is one that utilizes cloud computing to its fullest. Such applications are deployed as microservices within containers, and are dynamically managed. Some definitions now. Microservices is when an application is broken up into many loosely coupled components deployed on different servers so each component can be scaled up depending on its need. ‘Containers’ provide the ability to isolate each microservice deployment independently and provide for various out-of-the-box functionality such as portability, reliability, scalability. And ‘dynamically managed’ refers to support such dynamic scheduling and managing all the containers.