Continuous deployment

304 views
251 views

Published on

Just uploaded this for someone but i see that animations are broken. The slide is also not that usefull currently as it requires some more explanations.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
304
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Continuous deployment

  1. 1. Continuous DeploymentMartin Shwalbe
  2. 2. How Long does it take to Deploy? More than a Year?Six months to a Year? One to six months? Two Weeks to a Month? One day to two Weeks?One hour to one day? One day to two Weeks? Less than 10 Minutes?
  3. 3. How Long does it take to Deploy?
  4. 4. Continuous Deployment is a repeatable methodology to deploying code
  5. 5. Continuous Deployment is Automation
  6. 6. Deployment Reduces Code Inventory
  7. 7. Deployment improves Confidence
  8. 8. Continuous Deployment is Safety
  9. 9. Fast Turnaround leads to Happy Customers
  10. 10. … and happy developers
  11. 11. Traditional Release Cycle Timeline 1-4 WeeksDevelopment Release Cut Stage QA Fix Bugs Integrate Release! Patches
  12. 12. Continuous Deployment Release Cycle Timeline 5-10 Minutes Automated QADevelopment x x Release Cut Stage x Testing and Fix Bugs Staging x Integrate Patches Deploy Release!
  13. 13. ToolsJenkins Statistic Analysers
  14. 14. Database Evolution inContinuous Deployment Updating Database is 
  15. 15. Database Evolution
  16. 16. Database Evolution Categorize
  17. 17. Database Evolution: AdditionAddtions do not cause any problems.
  18. 18. Destructive Database EvolutionDestructive changes need a bit more care, the degree of which depends on the degree of destruction involved
  19. 19. Destructive Database EvolutionUnhappy Customer!
  20. 20. Database Evolution Which comes first?Code or the Database?
  21. 21. Destructive Database EvolutionApply Changes without breaking backwards compatibility
  22. 22. Destructive Database EvolutionThe application can still read and write to the old columns
  23. 23. Destructive Database EvolutionUpdate the application.//Keep this RequestSelect Address Datafrom Table User//Additional RequestSelect Address Datafrom Table Address
  24. 24. Destructive Database EvolutionThe application would read and write to both tables.
  25. 25. Destructive Database Evolution Cleanup the Application.SQL Script to copy old data from User table Select Address Data to Address table from Table Address
  26. 26. Destructive Database EvolutionDelete the obsolete Columns
  27. 27. Thank you!

×