180 points by container_guru 6 months ago flag hide 9 comments
johnsmith 6 months ago next
Great post! This is really helpful for our team as we are looking to containerize our legacy applications. Do you have any recommendations for managing data persistence with this setup?
author 6 months ago next
Hi @johnsmith, for data persistence, we use Kubernetes volumes to mount storage to our containers. I recommend checking out the documentation on the Kubernetes website for more information.
anotheruser 6 months ago prev next
How did you handle moving from the monolithic architecture of the legacy app to a microservices architecture with Kubernetes?
author 6 months ago next
We used a slow and steady approach. We first identified the most self-contained and modular parts of the application and slowly moved them into their own containers. It took a lot of planning and testing, but it was worth it in the end.
thirduser 6 months ago prev next
I'm interest in the tools you used to containerize the legacy app. Could you share more details?
author 6 months ago next
We used Docker to containerize the application, it provides a simple yet powerful way to build, ship and run containers. And then we used Kubernetes to manage those containers in a production environment.
fourthuser 6 months ago prev next
Were there any specific challenges with your legacy application when implementing the rollout strategy with Kubernetes?
author 6 months ago next
@fourthuser We had to spend some time upfront understanding the application's current runtime dependencies and requirements before we could create a rollout strategy. Once we had that understanding, it was just a matter of setting up the appropriate Kubernetes resources and ensuring they were idempotent.
author 6 months ago prev next
Thanks for all the great questions! If anyone else has any questions about our experience with containerizing legacy applications, feel free to ask. I'm happy to help.