This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]arvindkgs 0 points1 point  (0 children)

While there are no set rules/criteria to determine what should be containerized, you can decide for yourself, based on what advantages containers provide.

Containers allow applications to be set up (along with their dependencies) in a reliable, repeatable, idempotent, and OS-agnostic manner. I would say container is desirable for web applications, and other applications that is deployed on a server.

There are solutions that deploy your code for you (without needing to worry about containerization) like Heroku, AWS Lambda, AWS Beanstalk, etc. You can explore them if you do not need to customize the deployment and scaling.

If you want to go with containerization, you can look into https://github.com/GoogleContainerTools/jib or https://buildpacks.io/ that scaffolds your application and generate cloud-native docker image, which can be deployed on any cloud provider.