NYC Continuous Delivery Meetup - Introducing delta
3 likes•816 views
Michael Bryzek's presentation covers the implementation of continuous delivery using tools like Travis, GitHub, Docker, and AWS at Flow Commerce. He introduces Delta, an open-source solution designed for automated deployment stages focusing on audit and transparency, and outlines its architecture and usage. The talk emphasizes best practices in software deployment and the importance of maintaining a robust continuous integration pipeline.
NYC Continuous Delivery Meetup - Introducing delta
- 1. Continuous Deliveryw/ Travis,Github, Docker, and AWS Michael Bryzek [email protected] / @mbryzek Cofounder / CTO Cofounder / ex-CTO Gilt Groupe NYC Continuous Delivery Meetup June 1 2016
- 2. FlowCommerce Flow is a next-generation solution for taking merchants global - more at https://flow.io We are about to launch and are hiring – email [email protected] if interested
- 3. Why this Talk Many of our friends in the community saw a glimpse and asked if we could share more Paolo presented this year at PG Conf NYC on psql work – and lots of people expressed interest in CD We are thrilled to introduce delta today
- 4. as of tonight, delta is open source and still earlyenough to contribute github.com/flowcommerce/delta
- 5. Key Insight CD systems shouldfocus on audit and transparency Not an opinionated way to do things
- 6. Deploys at Flow aretriggered automatically by newtags Newtags arecreatedautomatically By MergingPullRequests
- 7. Livedemo
- 8. Delta Architecture UI: playframework/scala webapp that speaks only to API REST API in playframework/scala + akka - http://apidoc.me/flow/delta Postgresql
- 9. Key stages of Continuous Delivery
- 10. Stage 1:Sync Shas For each repository, keep a list of all of the unique shas
- 11. Stage 2:Synctags For each repository, keep a list of all of the unique tags
- 12. Stage 3:tag Automatically apply a new tag whenever the latest tag does not point to HEAD For delta, we assume semantic versioning (x.y.z), and each auto applied tag increments the micro version
- 13. Stage 4:Set Desired State Declare which tag should be in production
- 14. Stage 5:Builddocker image Automatically build docker images for every tag in desired state
- 15. Stage 6:scale Once docker image is ready: Create new cluster running new version Once healthy, move traffic Scale down old version
- 17. Delta Event Log Continuous delivery
- 19. Usageat Flow select avg(count), stddev(count) from (select date_trunc('week', journal_timestamp), count(*) from journal.build_desired_states group by 1) m; Releases: >1500 Weekly: > 100 Team size: 5 Thank you to: github.com/gilt/db-journaling
- 20. Delta Roadmap Deploy branches other than master Dependency support within a repo Smarter traffic management Better healthchecks More settings (enable/disable build in UI) UI / UX Improvements Contributors welcome and encouraged!
- 21. What aboutContinuousIntegration? We use travis-ci, and merge pull requests when all automated tests pass
- 22. OCD UpdateFridays Micro service architectures need to be constantly maintained Every Friday, we update all projects to latest versions of every library Enabled by another Flow open source project: github.com/flowcommerce/dependency
- 23. “Delta deploys itselfwhile deploying almost all of our applications onOCD Update Days at Flow”
- 24. Continuous Delivery Has Become a BasicNeed
- 25. ThankYou Michael Bryzek [email protected] / @mbryzek Cofounder / CTO Cofounder / ex-CTO Gilt Groupe Flow is Hiring – email [email protected] github.com/flowcommerce/delta
- 26. APPENDIX
- 27. DecouplingDeployment fromRelease “We recommend strictly using the term Deployment when referring to the act of deploying a change to application components or infrastructure. The term Release should be used when a feature change is released to end users, with a business impact.” https://www.thoughtworks.com/radar/techniques