Towards a responsive business - DevOps MeetUp Melbourne 2013
1 like576 views
The document discusses the challenges faced in software development, particularly issues related to architecture, automation, and quality. It emphasizes the complexity in building systems and the importance of managing this complexity through effective pipelines and automation tools. Key solutions include leveraging packaging, deployment automation, and rigorous testing to ensure responsive and reliable applications.
Towards a responsive business - DevOps MeetUp Melbourne 2013
- 1. TOWARDS A RESPONSIVE BUSINESS The Developer Way
- 7. “We make a change in one place and somewhere, something else breaks”
- 8. “It feels like it takes a long time to complete what should be a simple thing”
- 9. “Feels like all we have done are patches, hacks and short term tactical fixes to meet deadlines”
- 10. Part of any problem is: people & process
- 11. I’m going to focus on the technical parts
- 12. www.laputan.org
- 13. 1. Architecture 2. Automations 3. Quality We’ll talk about getting responsive in 3 levels …and what we learnt along the way.
- 14. 1. Architecture
- 15. Kitchen Sink
- 16. Legacy systems grow arms and legs… …because the world needs to continue
- 18. Factoring systems by Value Stream
- 20. You aren’t going to get it right at first go
- 21. Using WebAPI and Areas to build services within a service
- 23. Eliminating batch processes is hard
- 24. 2. Automations
- 25. “I do believe that complexity is the enemy. Un7l we be9er understand complexity, our chances of building be9er IT systems is limited. The first thing we must understand about complexity is that not all complexity is equal. And the complexity on which most people focus is probably the least complex complexity of all.” h4p://simplearchitectures.blogspot.com/2009/03/cancer-‐of-‐complexity.html Roger Sessions
- 26. Accidental complexity vs Planned complexity
- 29. Make it Visible!
- 30. Raw Materials i.e GIT Factory i.e CI Server Warehouse i.e ProGet /Nuget Distribution Network i.e. Powershell etc. Retailer i.e. Target Environment Use an Analogy
- 31. Drilling down...
- 32. to package our apps
- 33. What’s inside the nuget package? Puppet manifests Environment ConfiguraOons as JSON Install Script in Powershell Zip’ed up applicaOon
- 34. Proget to manage the packages for the environments Dev Feed Test Feed Staging Feed Production Feed
- 35. Push button deployment 1. Deploy v0.1.7 to staging 3. Install version v.0.1.7 4. Proget Staging Feed, give me, v0.1.7 6. Unpacks the box and runs the install script 2. Powershell over winRM 5. Here you go! Target Server
- 36. Checks for the correct environment Uses the environment configuraOon with puppet to configure the environment IIS configuraOon, Folder permissions etc
- 37. 3. Quality
- 38. Testing deployment scripts… …with Canary packages
- 39. Guarantees at every every stage in pipeline ü Unit Tested ü IntegraOon Tested ü BlackBox Tested
- 40. Status Checks
- 41. End-to-End tests
- 43. 5 Months +scope 9 weeks +scope 4 weeks +scope
- 47. Build Farm S3 Bucket Nigel’s Laptop Puppet & AWS scripts Cloud FormaOon APIs Packaged Scripts Create Machine Self Configured Behind the scenes
- 49. App Server Cloud FormaOon APIs Behind the scenes GO Server Self Configured Puppet & AWS scripts
- 51. 1. Architecture 2. Automations 3. Quality Recap
- 52. Thank you.