Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Some Lessons Learned for Faster App Delivery - ...

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.

Docker PDX

June 06, 2016
Tweet

More Decks by Docker PDX

Other Decks in Technology

Transcript

  1. how long does it take YOU to ship 1 line

    of code into production?
  2. os, lang & infra coupled os & lang coupled n-tier

    2000s service oriented 2010s completely decoupled micro services 2020s sw architecture is evolving
  3. 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
  4. 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
  5. microservices @ Shippable availability bug life 95% to 99.99% 3

    wks to < 3d deployments 1/wk to > 50/wk costs 44K to 4K
  6. 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
  7. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI

    DB traditional Deliveries Billing Products Inventory users
  8. transformation to microservices middleware (CRUD + workflows) Accounts Orders UI

    DB traditional modern reverse proxy Deliveries Billing Products Inventory users
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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)
  14. 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
  15. 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
  16. join our customers who run more than 100K builds per

    month try it @ content.shippable.com/portland-meetup