The Run Anywhere mindset is a new way of thinking about how to develop and deploy applications. By adopting this mindset, you can accelerate your development cycles, save money, and streamline your processes. This talk will explain the Run Anywhere mindset, explore its benefits, and discuss how to achieve Run Anywhere, as well as next steps after achieving this.

1. The
“Run Anywhere”
Mindset
Michael Mucciarone

2. About Me
• Grew up in Florida
• Alma Mater: Baylor University
• DevOps Engineer @ Capital One
• Docker & Automation Enthusiast
• Musician
• Video & Effects Editor
• Avid Science Fiction/Fantasy reader
• Gamer

3. Who is Capital One?
• More than just credit cards (Auto Lending,
Retail Banking, Commercial Banking, etc.).
• Startup in bank years. Still founder lead.
• All in on DevOps.
• We are Cloud first and aggressively moving
into the Cloud.
• Open sourcing some of our own products
(Hygieia / Cloud Custodian). We both leverage
and contribute to open source.

4. Overview
• What is “Run Anywhere?”
• Benefits of “Run Anywhere”
• How to achieve “Run Anywhere”
• What to do with “Run Anywhere”

5. What is “Run Anywhere”?
“I want to run. I want to hide.
I want to tear down the walls that hold me inside.”
–U2, Where the Streets Have No Name

6. Run Anywhere Mindset
•Containers
•Dependencies Included
•Operating System Agnostic
•Hardware Agnostic
•Location Agnostic

7. Run Anywhere in Practice
•Local for Development
(or demonstrations)
•DEV Environment
•QA / Test / Staging
•Production

8. Benefits of “Run Anywhere”
“I’ll be here when you are ready to roll with the changes…”
–REO Speedwagon, Roll with the Changes

9. Development
•Develop completely locally
•Develop disconnected
•Minimize external
development dependencies
•Develop against the target
architecture
•Develop against other
applications

10. Deployment
•Once Development is complete, package
the code in a Docker Image
•Deployment Flexibility
•Portability
•Server installs simplified

11. Cost Savings
•More efficient resource
usage
•Better Scaling
•Simplified maintenance
•Lower Licensing costs

12. How do I achieve “Run Anywhere”
“Carry on my wayward son; There’ll be peace when you are done…”
–Kansas, Carry on Wayward Son

13. Containerize, Containerize, Containerize…
•Don’t Lift, Shift and Bottle
•Think Microservices
•Enables the “Run Anywhere”
Mindset
•Containerized = Highly Portable

14. Pay Down Technical Debt
•Tech Debt will slow you
down
•Tech Debt will limit your
run anywhere flexibility

15. Tech Debt Paydown: Where to Start
•Refactor applications for newer
technologies / languages
•Update Application Dependencies
•Add Health Checks
•Service Discovery
•Consul, Netflix Eureka
•Externalized Configuration
•Etcd, Consul

16. Review & Refine your CI/CD processes
• Create scripted CI & CD Pipelines
• Pipeline Libraries are your Friend
• Make your build jobs user friendly
• Build your Pipelines for
“somebody else”

17. Application Builds (CI)
•Remove any unnecessary steps
•Update your build automation tools (Maven,
Gradle, npm, etc )
•Test, test, and test
•Version Every Build
•Script your pipeline

18. Deployments (CD)
•Remove Unnecessary Steps
•Parameterize your Deployments
•Remove Deployment Friction
•Add Deployment Metadata
•Environment Manifest
•Service Discovery
•Script your pipeline

19. Image Building Guidelines
•Start with a small Base Image
•Minimize the number of Layers
• Use multi-stage builds
•Exclude files/folders with a
.dockerignore

20. Image Safety Guidelines
•Only use trusted base
images!
•Pre-scanned for malware
• Docker Trusted Registry
• Xray for Artifactory
• Scanned by Docker Hub

21. What NOT to do when Building Images
• Don’t install unnecessary packages
• Don’t run SSH/Telnet
• Don’t create large images
• Don’t pass `/` as the build context
• Don’t run as root
• Don’t rely on community images

22. What do I do once I’ve achieved
“Run Anywhere”?
“Oh, the movie never ends; it goes on and on and on and on…
–Journey, Don’t Stop Believing

23. Container Deployment Journey
•Start Simple: Instance with a Container
•1 container/instance
•Very Low Risk
•No re-architecting required
•Move up to docker-compose
•Instance with Multiple Containers
•Might be able to eliminate some instances
•Move to a Container Orchestrator

24. What is an Orchestrator
•Manages Containers
•Usually runs on a Cluster
•Monitors Container Health
•Self-healing
•Provides Load Balancing
•Provides Service Discovery

25. Container Orchestration Platform Options
•Kubernetes
•Docker Enterprise Edition
•DC/OS from Mesosphere
•Container IaaS

26. In Summary…
“This was a triumph. I’m making a note here, ‘Huge Success!’
It’s hard to overstate my satisfaction. ”
–GLaDOS, Still Alive, Portal

27. The Run Anywhere Mindset
•Container with Dependencies
Included
•Benefits of Run Anywhere
•How to achieve Run Anywhere
•What to do after achieving Run
Anywhere

28. Questions?
“Is this the real life? Is this just fantasy?”
–Queen, Bohemian Rhapsody

29. Thank You
https://www.linkedin.com/in/michaelmucciarone