JaxDevOps Experience Round-Up
I was lucky enough to be a speaker at JaxDevOps, a great opportunity for me to meet other devs, hear how others are tackling complex architecture problems, and of course talk about some of the awesome things we’ve been doing.
Join the DZone community and get the full member experience.Join For Free
last week i was lucky enough to be a speaker at jaxdevops london. this was a great opportunity for me to meet other devs, catch-up with some of our technology partners ( thanks digitalocean for the swag! ), hear how others are tackling complex architecture problems, and of course talk about some of the awesome things we’ve been doing at cloud 66. a huge thanks to the jax team, who did a fantastic job organising the event.
alongside presenting, the best part was getting a chance to sit-in on some great presentations - including the talk from john davies from c24, who covered blockchain (the foundational technology supporting bitcoin) and the role smart contracts will play in innovating future banking apps.
one of the other heavily attended sessions was the talk given by mike mcgarr from netflix, whose presentation dived into the company’s engineering culture and the lessons they'd learnt from migrating their platform to the cloud.
another big conference theme was everything containers-related. laura frank from codeship spoke about the importance of clean code and making sure to include testing frameworks when introducing docker into your workflow.
how to run docker in production was the main feature of my presentation, which focused on practical tips for deploying containers at scale. so for those who missed the talk, here's a recap of my top 7 tips:
- start with the core component you’re going to need - your container image, making sure it’s small, secure, performant, stable and immutable
- for consistency, plan to use the same image across the dev/test/stage and production stages of your development lifecycle
- build images so they’re lightweight and avoid adding in any unnecessary components that defeat running containers
- make your life easier by using one of the many docker buildflow tools in the market ( cloud 66 has a great one!!! : ))
- once your image is built, the next step is to orchestrate its dependent parts by establishing your workflow
- and to run and scale in production, you’ll need to make some decisions about how to provision your containers
- and finally, be methodical about how you approach building with microservices and docker. it’s very easy to get sidetracked by ‘technology noise’
containers allow infinite freedom when it comes to mixing and matching your application code with microservices. keep in mind that learning docker is just like learning any other new, fast-paced technology; it’s going to require a learning curve. the journey from your first ‘hello world’ all the way to running docker at scale is likely to be fogged by technology noise. that noise can cloud your vision and workflow, so it's really important to stay focused.
and also remember, containers aren’t vm’s and docker is really just a methodology for breaking down app architecture. it won’t deploy your app by itself. but luckily, we can help you with that .
Published at DZone with permission of , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.