![]() ![]() Moving to containers and Kubernetes just for the sake of doing it can actually introduce a lot more scope and technical challenges, depending on the applications and the teams running them. Don’t do it just because you can or you want, Migrate existing Pega applications into containers with a long-term vision in mind. * Why and whether you choose Pega in bare-metal cloud computing engine vs container platform.įirst, make sure your decision to containerize an existing monolithic Pega application and operate it with Container platform/Kubernetes is a sound choice. * Strategy for choosing cloud platform (private cloud/ public cloud, vendor, platform, etc). This article tries to cover strategies, consideration and planning of containerization of the application and App server component of a Pega platform, and it does not cover below * You are starting a new Pega project/application and from day one you want to run in container as part of the Pega cloud journey. * You are already operating your Pega application in a cloud environment, and now you want to containerize and run in a container platform, * or you have already made your mind to deploy your existing Pega application (running in on-premises bare metal server) in a container environment. This article assumes that you are in any one of the below stages with your Pega application journey This article is intended to guide on what you should consider and how you should plan to migrate or deploy your Pega application in a container platform (Kubernetes or any other container orchestration platform). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |