Some Lessons Learned for Faster App Delivery - Tom Trahan

Continuous Integration (CI) helps developers and ops teams ship more code faster. And with Docker, the pains of friction between these two groups is radically reduced by having predictable reusable environments. Tom will talk about how teams can think about this new world of application pipelines, show how CI works in Docker with Shippable, and shares some of our experiences in implementing Docker to accelerate application delivery.

om Trahan is the VP, Business Development of Shippable, a venture-backed startup providing hosted continuous delivery platform built on containers. Previously, Tom was Co-Founder and CEO of EnterPAS, a software startup providing records management and change control for FDA-regulated companies, a director at Microsoft focused on IT enterprise application development and operations, and a consultant at SAP. Tom spends his free time with his wife and two boys, coaching youth sports, traveling and playing guitar. You can find him on Twitter as @Tom_Trahan.

Transcript

1. Docker Meetup June 6, 2016 some lessons learned for faster app delivery
2. tom trahan vp, business development tom@shippable.com @tom_trahan how continuous delivery is done
3. a devOps parable Nate gets it running in dev rgm1(1)
4. a devOps parable Nate gets it running in dev rgm1(1)
5. a devOps parable (part2) Angelica gets it running in test rgm2(2)
6. a devOps parable (part2) Angelica gets it running in test rgm2(2)
7. a devOps parable (part3) Bob deploys it to prod rgm3(3)
8. a devOps parable (part3) Bob deploys it to prod rgm3(3)
9. whoever innovates fastest wins
10. question for the room… what parts of DevOps change significantly in a Dockerized world?
11. how long does it take YOU to ship 1 line of code into production?
12. how do you overcome the obstacles? devOps? automation? architecture? culture change?
13. os, lang & infra coupled os & lang coupled n-tier 2000s service oriented 2010s completely decoupled micro services 2020s sw architecture is evolving
14. our problems • higher complexity • bugs harder to find and fix • forced homogeneity • scaling was all or nothing • every change required complete regression testing • continuous deployment nearly impossible
15. microservices to the rescue split your application into smaller services that each perform one business function
16. simplicity each microservice can be maintained independently by a small team
17. independence each microservice can be deployed independently
18. scale each microservice can be scaled up or down as needed
19. scale each microservice can be scaled up or down as needed
20. availability bugs only affect parts of the application and can be fixed quickly
21. heterogeneity team can choose language, technology, tools that are best for the service
22. faster testing only the microservice that changed needs to be tested
23. easier continuous delivery each microservice has its own delivery pipeline ui api db ui api db code continuous integration ui api db api ui api db api ui dev test prod deployment pipelines
24. microservices @ Shippable availability bug life 95% to 99.99% 3 wks to < 3d deployments 1/wk to > 50/wk costs 44K to 4K
25. 6 tips to move to microservices • move to a distributed source control system • build new functionality as a microservice • convert existing components gradually • containerize your application • implement CI/CD • invest in monitoring
26. transformation to microservices users
27. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI DB traditional Deliveries Billing Products Inventory users
28. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI DB traditional modern reverse proxy Deliveries Billing Products Inventory users
29. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI DB traditional modern REST API (CRUD) Audit New UI reverse proxy Deliveries Billing Products Inventory message Bus (workflows) Audit users
30. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI DB traditional modern REST API (CRUD) Audit New UI reverse proxy Deliveries Billing Products Inventory message Bus (workflows) Audit Products users
31. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI DB traditional modern REST API (CRUD) Audit New UI reverse proxy Deliveries Billing Products Inventory message Bus (workflows) Audit Products Inventory Inventory users
32. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI DB traditional modern REST API (CRUD) Audit New UI reverse proxy Deliveries Billing Products Inventory message Bus (workflows) Audit Products Inventory Inventory Billing Billing users
33. but, increasing complexity
34. but, increasing complexity rgm1(1) rgm2(2) rgm3(3) rgm4(4) rgm5(5) rgm6(6) rgm7(7) rgm8(8) rgm9(9) rgm10(10)rgm11(11)rgm14(14) rgm13(13)rgm14(14)rgm15(15) rgm16(16)rgm17(17)rgm18(18)
35. dramatically helped with containers and CI/CD pipe 1 pipe 2 pipe 3 pipe 4 pipe 5 pipe 6
36. demo container-based pipelines into Docker Datacenter
37. simplified with mono-repo mono-repo prod dev test pipe 1 pipe 2 pipe 3 pipe 4 pipe 5 pipe 6
38. benefits we’ve seen with mono-repo Better developer testing Reduced code complexity Effective code reviews Sharing of common components Easy refactoring The results? Our productivity has increased at least 5x, while still reaping the benefits of microservices
39. demo mono-repo pipelines into Docker Datacenter
40. BUILD SHIP RUN Shippable enables 
 the real-time, iterative org … Infra & Tools flow + decision to ship? flow + decision to ship! Build Tools Linux/Docker-based Artifacts Hosted Artifacts On-Prem IaaS PaaS CaaS Public IaaS PaaS CaaS Private Build Environments Shippable/Hosted/On-Prem CI/CD SaaS Hybrid/On-Prem
41. join our customers who run more than 100K builds per month try it @ content.shippable.com/portland-meetup
42. thank you ship code faster @ www.shippable.com