| | SEPTEMBER 20248CIOReviewMIGRATING TO CONTAINERS USING COULD VENDOR OFFERINGSBy Hiram Amador, Manager of Data and Cloud Operations, Fragrance.comOne of the current debates when it comes to migrating applications from a non-container centric model to a cloud native approach is whether to take advantage of cloud vendor offerings. Most of my experience is with Amazon Web Services (AWS), so the example I will use will be around AWS bases services. Google Compute Platform and Azure offer mainly managed Kubernetes as a service, which might have preconfigured hooks into other vendor specific services. My perspective in this article is that of a platform engineer offering bridge services to application owners. My role is to offer services to the application owner and handle specifics of cloud management so that application owners can focus on the business functionality of their software product.The best way to consider migrating applications and workloads into cloud native systems is to determine whether vendor cloud offerings could simplify development in the short term and allow an application to be containerized with little overhead. The end goal of cloud migration efforts should be to move application architecture to current day best practices. One of the issues with going straight to this end goal is that legacy applications might have widely divergent philosophies from philosophies that are emerging as container technology continues to evolve. To this end, sometimes the best approach is to incrementally modify the application so that it can function as a container without expecting a fully matured Kubernetes infrastructure. Since Kubernetes is not very opinioned and is being expanded with each release, it can Hiram AmadorIN MY OPINION
< Page 7 | Page 9 >