Dockerizing Rails

This introduces the concepts of Docker to the application developer. This is how one can go from a proof of concept to a resilient application under load

Transcript

1. Dockerizing Rails
2. Dockerizing Rails …or any other framework
3. Why Dockerize? ◎ Have many commands do you use to setup your development environment? ◎ How easy is it to deploy your app? ◎ How much downtime does your deploy cost? 3
4. Hello! I’m Igbanam ◎ S.S.E at Andela ◎ Poet ◎ @yaasky on Twitter 4
5. “ dockerizing apps repeatable deployments at your fingertips 5
6. 0. Zero Downtime What and Why 6
7. “ The standard for website availability is the five nines 99.99999% uptime 7
8. Deployments 8
9. Today, we shall talk about ◎ Rails ◦ Fast Prototyping ◦ Continuous Deployment ◎ Docker ◦ Compose ◦ Swarm (vs. Kubernetes) ◎ Live Deployments ◦ Demo 9
10. 1. Ruby on Rails Most popular Ruby framework 10
12. 12 Ruby on Rails Principles ◎ Programmer Happiness ◎ Convention over Configuration ◎ Progress over Stability More at Rails Doctrine
13. Release Pipeline Code Test Deploy 13
14. Deployment pipeline 14 Production 1 SCM Development
15. 2. Docker Containerizing 15
16. 16 Brief History of Deployments ◎ FTP (Shared Hosting) ◎ Rsync ◎ SSH + Script ◦ Ruby’s Capistrano ◎ Virtual Machine ◦ Platform-as-a-Service ◎ Containers
18. Virtualization ◎ Hardware-level ◎ Heavyweight ◎ Slow provisioning ◎ Limited Performance ◎ Fully isolated ◎ More secure Difference between Virtualization and Containerization Containerization ◎ OS-level ◎ Lightweight ◎ Real time provisioning and scalability ◎ Native performance ◎ Process-level isolation ◎ Less secure (ish) 18
19. 19 Images Container Engine Swarm
20. Docker Constituents ◎ Images ◎ Containers ◎ Engine ◎ Swarm Image An image is a blueprint of a machine. Here we describe configurations and constituents of the machine. Think of it as a “class” 20
21. Dockerfile (snippet) 21
22. Docker Constituents ◎ Images ◎ Containers ◎ Engine ◎ Swarm Container A container is an instantiated image. Complete isolated process environment where the service (your app) runs. 22
23. Container Build Process 23
24. Docker Constituents ◎ Images ◎ Containers ◎ Engine ◎ Swarm Engine Containers need a host machine to run on. The engine serves this purpose. 24
25. Engine Evaluation 25
26. Docker Constituents ◎ Images ◎ Containers ◎ Engine ◎ Swarm Swarm A collection of engines (as nodes) within a cluster. Also an orchestration tool for deployments 26
27. Docker Constituents Volumes Filesystems within your containers Nodes Engines within a Swarm Stacks Managing services in a swarm. Compose is the definition. Services …provided by the container. This could be your app. Networks Define the topology of your platform. 27
28. Docker Hub Repository for Docker Images. Opensource, and free. hub.docker.com 28
29. 3. Docker + Rails Let's put our app in a box 29
30. Small ToDo App (Underbelly) Read Database (SQL) Write DB (NoSQL) Cache (Redis) MSG Broker (Kafka) API Server (Rails) Logs Monitoring Tools 30
31. “ “Logic Complexity is solved with abstraction. Process Complexity is solved with automation.” ~ I’m paraphrasing Uncle Bob 31
32. Docker Compose Orchestrate everything. Let the computer compute. 32
33. 4. Scale Small App, Big Cloud 33
34. Successful Software Setups Processes Team Architecture 34
35. Three Pillars of Good Software Team ◎ Conway's Law ◎ Agile teams ◎ Autonomy Processes ◎ Collaboration ◎ Testing ◎ Releases Architecture ◎ Monolith ◎ Distributed ◦ Microservices 35
36. Monolith or Microservices 36 or Monolith by Rene Aigner Stonehenge by Unknown
37. “ You are the “Dev” in DevOps 37
38. Swarm ◎ Familiar API ◎ Built on building blocks ◎ Optimized for speed ◎ Built-in load-balancing ◎ Volumes across containers ◎ Automatic Network Config ◎ Self-discovery within cluster 38 Swarm vs. Kubernetes Kubernetes ◎ Novel API ◎ Isolated Concept ◎ Optimized for resilience ◎ Manual load-balancing ◎ Volume within pods ◎ Manual Networking ◎ Containers muse identify
39. Thanks! Any questions? @yaasky 39