Radar: Integrate to Innovate: Continuous Delivery
•Télécharger en tant que PPTX, PDF•
1 j'aime•657 vues
The document discusses the history and benefits of continuous delivery practices for software development. It describes how processes have evolved from manual and waterfall approaches to incorporating continuous integration, deployment automation, and infrastructure management. Continuous delivery is presented as improving agility, reducing costs and development time, and increasing software quality and availability through process automation. A maturity model is provided for assessing continuous delivery capabilities.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Radar: Integrate to Innovate: Continuous Delivery
Similaire à Radar: Integrate to Innovate: Continuous Delivery (20)
Plus de Michael Medin
Plus de Michael Medin (20)
Dernier
Dernier (20)
Radar: Integrate to Innovate: Continuous Delivery
- 1. © Connecta – Michael Medin Continuous Delivery Connecta Stockholm, 2014-05-22
- 2. © Connecta – Michael Medin DEVELOPER CONTINUOUS MICHAEL MEDIN delivery OUTSIDE THE BOX
- 3. © Connecta – Michael Medin Platinum Gold Silver Remarketer 2009 2010 2011 2012 Fusion MiddleWare: Partner of the year 2011 2012 Fusion MiddleWare: Most Certified Implementation Specialists Speaker and Keynote at many Conferences and Partner Events In the Oracle SOA Suite 12c Beta program 2013
- 4. © Connecta – Michael Medin Service Oriented Architecture Application Integration Architecture WebLogic/Exa Siebel CRM CRM On Demand BI
- 5. © Connecta – Michael Medin 2014 Challenges INTEGRATION
- 6. © Connecta – Michael Medin SOA REST MOBILECLOUD HYBRID CLOUD PRIVATE CLOUD Integration GATE WAYS API
- 7. © Connecta – Michael Medin Hybrid integration platform capabilities Cloud On- premises Existing Silos New Silos
- 8. © Connecta – Michael Medin COMPLICATED MORE
- 9. © Connecta – Michael Medin What’s the link? GLITCH
- 10. © Connecta – Michael Medin GMAIL OUTAGE 2014-01-14 NEVER FORGET
- 11. © Connecta – Michael Medin WHOS TO BLAME? WE ARE!
- 12. © Connecta – Michael Medin AVALIBILITY INCREASED COMPLICATED MORE
- 13. © Connecta – Michael Medin OUT SOURCING CUTS CUSTOMERS OFF SHORING CHANNELS INNOVATION Cost? SERVICES NEAR SHORING
- 14. © Connecta – Michael Medin perspectives most significant external pressures Source: IBM C-suite Study http://www-935.ibm.com/services/us/en/c-suite/csuitestudy2013/
- 15. © Connecta – Michael Medin Cost? Innovation Facilitating
- 16. © Connecta – Michael Medin AVALIBILITY INCREASED COMPLICATED MORE COST REDUCED
- 17. © Connecta – Michael Medin CHANGE TIME FOR
- 18. © Connecta – Michael Medin DELIVERY CONTINUOUS HISTORY
- 19. © Connecta – Michael Medin 1990: Classic software development Gather Requirements Write Specification Build software Test software Deliver Software Acceptance Test Done
- 20. © Connecta – Michael Medin 2000: Iterative projects Gather Requirements Write Specification Build softwareTest software Deliver Software Acceptance Test
- 21. © Connecta – Michael Medin 2000: Modularized architecture Frontend Business logic Backend
- 22. © Connecta – Michael Medin 2000: Agile projects not code Gather Requirements Write Specification Build softwareTest software Deliver Software Acceptance Test
- 23. © Connecta – Michael Medin 2000: Waterfall Waterfalls Frontend Business logic Backend
- 24. © Connecta – Michael Medin INTEGRATION CONTINUOUS
- 25. © Connecta – Michael Medin Continuous Integration Code IntegrateBuild Test
- 26. © Connecta – Michael Medin 2010: Enterprise Development Code IntegrateBuild Test Code IntegrateBuild Test Code IntegrateBuild TestCode IntegrateBuild Test Mobile Integration ERPCRM
- 27. © Connecta – Michael Medin 2020: Agile Enterprise Software development Code IntegrateBuild Test Code IntegrateBuild Test Mobile ERP Code IntegrateBuild Test Code IntegrateBuild Test CRM Code IntegrateBuild Test Integration
- 28. © Connecta – Michael Medin DELIVERY CONTINUOUS
- 29. © Connecta – Michael Medin Continuous Delivery Code Integrate Build Unit-test Deploy Acceptance/ Integration test Release
- 30. © Connecta – Michael Medin DELIVERY CONTINUOUS PRACTICE
- 31. © Connecta – Michael Medin AUTOMATE Code Test Release Install Configuration Deploy Acc. Test Migration Everything
- 32. © Connecta – Michael Medin PIPELINE DEPLOY WORKFLOW
- 33. © Connecta – Michael Medin HOW?
- 34. © Connecta – Michael Medin Best Practices Patterns Build Release Deploy Automate Smart Templates
- 35. © Connecta – Michael Medin Version Control Test Installation Configuration Maintenance Automate SetupGovernance
- 36. © Connecta – Michael Medin Your Your process Way
- 37. © Connecta – Michael Medin DELIVERY CONTINUOUS COST
- 38. © Connecta – Michael Medin FREE Pays it self There is a free lunch!
- 39. © Connecta – Michael Medin Deploy: Time: Consultants: 1 per week 3-4 20h Every week!
- 40. © Connecta – Michael Medin Accumulated cost for delivery 0 20 40 60 80 100 120 140 1 2 3 4 5 6 7 Manual Automated
- 41. © Connecta – Michael Medin Project cost after implementing Continuous Delivery 0 50 100 150 200 250 300 350 400 Project A Project B Project C Project D Project E Hours
- 42. © Connecta – Michael Medin Practice Build management and CI Environments and deployment Release management Testing Data management Configuration Management Level 3 – Optimizing: Focus on process improvement Teams regularly meet to discuss integration problems and resolve them with automation, faster feedback, and better visibility All environments managed effectively. Provisioning fully automated. Virtualization used if applicable. Operations and delivery teams regularly collaborate to manage risks and reduce cycle time. Production rollbacks rare. Defects found and fixed immediately. Release to release feedback loop of database performance and deployment process Regular validation that CM policy supports effective collaboration, rapid development, and auditable change management processes. Level 2 – Quantitatively managed: Process measured and controlled Build metrics gathered, made visible, and acted on. Build s are not left broken. Orchestrated deployments managed. Release and rollback processes tested. Environment and application health monitored and proactively managed. Cycle time monitored. Quality metrics and trends tracked. Non functional requirements defined and measured. Database upgrades and rollbacks tested with every deployment. Database performance monitored and optimized. Developers check in to mainlined at least once a day. Branching only used for releases. Level 1 – Consistent Automated processes applied across whole application lifecycle Automated build and test cycle very time a change is committed. Dependencies managed, Re-use of scripts and tools. Fully automated, self- service push-button process for deploying software. Same process to deploy to every environment. Change management and approvals processes defined and enforced. Regulatory and compliance conditions met. Automated unit and acceptance tests, the latter written with testers. Testing part of development process. Database changes performed automatically as part of deployment process. Libraries and dependencies managed. Version control usage policies determined by change management process. Level 0 – Repeatable: Process documented and partly automated Regular automated build and testing. Any build can be re- created from source control using automated process. Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned Painful and infrequent, but reliable, releases. Limited traceability from requirements to release. Automated tests written as part of story development. Changes to databases done with automated scripts versioned with application. Version control in use for everything required to recreate software: source code, configuration, build and deploy scripts, data migrations. Level -1 – Regressive Processes unrepeatable, poorly controlled, and reactive Manual process for building software. No management of artifacts and reports. Manual process for deploying software. Environment-specific binaries. Environments provisioned manually Infrequent and unreliable releases. Manual testing after development. Data migration unversioned and performed manually. Version control either not used, or check-in happens infrequently. Capability Maturity ModelLevel 1 Consistent Automated processes applied across whole application lifecycle Automated build and test cycle very time a change is committed. Dependencies managed, Re-use of scripts and tools. Fully automated, self- service push-button process for deploying software. Same process to deploy to every environment. Level 0 Repeatable: Process documented and partly automated Regular automated build and testing. Any build can be re- created from source control using automated process. Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned Level -1 Regressive Processes unrepeatable, poorly controlled, and reactive Manual process for building software. No management of artifacts and reports. Manual process for deploying software. Environment-specific binaries. Environments provisioned manually Level 1 Consistent Automated processes applied across whole application lifecycle Automated build and test cycle very time a change is committed. Dependencies managed, Re-use of scripts and tools. Fully automated, self- service push-button process for deploying software. Same process to deploy to every environment. Level 0 Repeatable: Process documented and partly automated Regular automated build and testing. Any build can be re- created from source control using automated process. Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned Level -1 Regressive Processes unrepeatable, poorly controlled, and reactive Manual process for building software. No management of artifacts and reports. Manual process for deploying software. Environment-specific binaries. Environments provisioned manually
- 43. © Connecta – Michael Medin DELIVERY CONTINUOUS BENEFITS
- 44. © Connecta – Michael Medin Agility Time To Market Iterative Lowerincreased reduced enterprise development cost Quality increased
- 45. © Connecta – Michael Medin Time MoneyQuality AUTOMATE REDUCE COST MORE TIME INCREASE AVALIBILITY
- 46. © Connecta – Michael Medin process product
- 47. © Connecta – Michael Medin THANK YOU
- 48. © Connecta – Michael Medin Events: Workshop Open World OOW Reunion 10 September September/October Q4 Middleware Consolidation & Innovation workshop Yogesh Sontakke
- 49. © Connecta – Michael Medin Our job is to automate business processes. Why do we do this manually?
- 50. © Connecta – Michael Medin Photo by Olga Berrios
Notes de l'éditeur
- Hej, jag heter Michael Medin Kommer från Connecta Skall prata om våra erfarenheter inom CD
- Men först: Jag heter (som sagt va) Michael Medin Brukar titulera mig som Arkitek men är Utvecklare Brinner för att bygga saker (lego, hus eller datorer spelar ingen roll) Älskar CD då det jag inte vill göra alla tråkiga saker Jobbar med integration/enterprise vilket gör att CD inte förekommer Men gillar ”out side the box” och brukar således hitta ett sätt att lösa det på
- Jobbar på Connecta och vi är Oracle partner. Började satsa på Oracle 2009 och sedan dess har det vart en snabb resa. Partner of the year 2011, 2012, 2013 Vi har flest impl. Specialists innom SOA I norden Vi är numera med i Oracle SOA 12c beta program (vilket är himla roligt)
- Vi har idag två ben: Där jag jobbar: SOA, AIA, Exa och så vidare Samt ett CRM/BI team men det kan jag inget om så fråga inte mig om det. Sen har vi massa kunder men det är inte det jag är här att prata om. Så nu har jag gjort min chef glad så kan jag återgå till min riktiga pressentation
- Utmaningar inom integration: 2014 Mycket har hänt de senaste åren som driver ett antal förändringar inom integrations området
- För 10 år sen när web-service var hipt-och-häftigt så trodde jag. Att så fort som vi landat detta och web service faktiskt fungerar mellan system och plattformar kommer integration bli enkelt Men sedan började cloud, rest osv dyka upp och då vart det hela tiden bara svårare och svårare
- Så här ser det ofta ut idag: Man har massa olika typer av system att integrera mot (Private, Silo, Public). Men har olika typer av integration (App, Data, B2B, Cloud) Så man kan lite kort säga att det blivit ”mer och mer komplicerat”
- Inte som jag trodde för 10 år sen: enklare och enklare
- Detta är några ganska stora och kända varumärken: Vad har de för gemensam nämnare? Dom hade alla ”problem” med IT under förra året. Och detta är stora företag som har ganska stora IT avdelningar och troligen ganska bra koll. För 10 år sen hade det inte varit något problem, för 5 år sen hade vi nog alla sagt ”ja men så är det”. Idag lever vi i en lite annan värld. Vi har börjat förutsätta att detta inte får faliera.
- Det som händer när IT systemen falierar idag är att det hamnar i tidningen: Vilket får ganska omfattande negativa PR effekter. Helt plötsligt är det inte längre en lekstuga…
- Självklart är det vårat fel… vi inom integration sitter i mitten och får alltid försvara oss…
- Så utöver att det blivit mer komplicerat. Så har även kravet på tillgänglighet ökat dramatiskt.
- Den sista delen är ”kostnad” vilket är ett lite dåligt ordval egentligen. För några år sen var det ganska vanligt med off-shoring och liknande för att minska kostnaderna. Idag ser man en del kunder som till och med för det motsatta. Det mera intressanta när det gäller kostnad är den andra sidan: De nya kanalerna, kunder och tjänsterna. Idag är det inte konstigt att man flyttar ut sitt affärssystem i mobilen och gör det tillgängligt 24/7. Detta kräver ett enormt integrations behov. Och när vi tidigare skulle bygga 20 integrationer mellan två system blir det idag kanske 200 och den kostanden kan man inte acceptera. Innovationen driver ner priset
- I en stor undersökning som IBM gjort visar att VD:s idag anser att teknik är den viktigaste faktorn. Inte marknaden eller ekonomi: Teknik. Detta är en drastisk förändring sen för 10 år sen då det var på plats 6
- Så kostnad är inte drivkraften, och troligen inte rätt ord. Innovation: är det vi behöver supportera:
- Men det kräver minskade kostander
- Så jag tror det är dags för oss att förändras
- Och istället för att titta på hur vi kan göra kan vi titta lite på hur andra gjort
- Iterative software development Not just iterative projects Increased Agility Reduced administration Reduced Time to market Decreased administration times Deployment Version management Increased Quality You know it works You know which version is where You know where the “source code is” Reduced Stress! You know it works
- Questions?
- Questions?