search
JAX DevOps has landed

9 tips from a pro: What we learned at JAX DevOps Day #1 about containers

JAX Editorial Team
JAX DevOps

JAX DevOps day one: the mechanical sympathy between Docker and Java, tips that might come in handy when dealing with containers and reasons why you should [or shouldn’t] containerize an existing (monolithic) app.

They say a picture is worth a thousand words so let’s find out how the day went from the first keynoter himself: Damon Edwards, co-founder and Chief Product Officer of Rundeck, Inc., the makers of the popular job scheduling and runbook automation tool, Rundeck.

 

OpenCredo’s Daniel Bryant took the stage and talked about continuous delivery and containers. Let’s start with the conclusion: you need to push everything through the pipeline ASAP. Confused? Remember these four lessons and you’ll be fine.

JAX DevOps 2017

It’s time to bring out the big guns — the lessons learned.

  1. Make your dev environment like production
  2. Dockerfile content is *super* important
  3. Talk to the sysadmin people — their operational knowledge is invaluable
  4. Metadata is valuable
  5. Beware of the “latest” Docker Tag (particularly in a CI environment)
  6. Security is super important for containers
  7. Tooling in the container space is becoming stable 
  8. Containers are not a silver bullet. When you want to move to containers, you probably ask yourself the following: Should I go all in?  The answer is No. The best way is to start with the basics because there’s so much going on with containers that you need to go slow. Plus, it will cost more if you don’t go incremental. 
  9. Containerize an existing (monolithic) app. Should you do it? Do yourself a favor — Check out the photo and then decide. 

Containerize an existing (monolithic) app

You thought we’d forget about Docker? No sir! Here’s why a mechanical sympathy is going on between Docker and Java.

 

Check back later for our coverage of JAX DevOps.

Comments
comments powered by Disqus