| We're in the process of migrating our (primarily) java services from straight AWS to kubernetes. At the beginning the author poses the following questions: * Do you use Mac, Windows, or Linux? Have you ever faced an issue related to \ versus / as the file path separator?
What version of JDK do you use? Do you use Java 10 in development, but production uses JRE 8? Have you faced any bugs introduced by JVM differences? * What version of the application server do you use? Is the production environment using the same configuration, security patches, and library versions? * During production deployment, have you encountered a JDBC driver issue that you didn’t face in your development environment due to different versions of the driver or database server? * Have you ever asked the application server admin to create a datasource or a JMS queue and it had a typo? I've experienced problems whose root cause are some form of all of those. Much of it could be chalked up to growing pains etcetera, but, for example, there are concrete differences between docker versions running on mac and linux that have shown up for me. This doesn't reduce the author's argument, but they do seem liked strange examples. Our choice to move to Docker and kubernetes came from developers, and specifically spoke to the need for consistent, reproducible test environments. We had dockerized most applications many months before the notion of using them in production was put on the table. What remains to be seen is if the switches in production reduce complexity and maintenance on the devops end of things, as well. I'm also curious how many other organizations had containers introduced 'from the bottom up' like us. |