Building a Service Delivery Infrastructure

Originally presented at Grace Hopper Celebration, 2019. Resilient, scalable, secure, and automated infrastructure accelerates the delivery of business value from software. How can we build an ecosystem that supports such mythical delivery? This session applies software
engineering and agile techniques to building a delivery ecosystem as a set of software products that serve the needs of software engineers and operations teams.

Transcript

2. Building a Service Delivery Infrastructure #GHC19
3. Paula Paul @paulapaultweets Slalom Build Distinguished Engineer Rosemary Wang @joatmon08 HashiCorp Developer Advocate 3 #GHC19
4. Building a Service Delivery Infrastructure Ecosystem #GHC19
5. 5 What is it? #GHC19
6. services & applications business capability delivered in 6 #GHC19
7. services & applications business capability delivered in 7 #GHC19 delivered by business value delivered on infrastructure
8. Delivery Infrastructure Ecosystem 8 #GHC19
9. 9 Given an identifier associated with a customer, When I call an API endpoint Then I should get the customer’s name. #GHC19 Deliver Me, "Hello Customer!"
10. 10 Given an identifier associated with a customer, When I call an API endpoint Then I should get the customer’s name. #GHC19 Deliver Me, "Hello Customer!" I need to...
11. 1 1 As a developer... #GHC19
12. I WANT TO BE PRODUCTIVE 12 #GHC19
13. 13 As a ... I want ... So that … More / less detail Consider acceptance criteria #GHC19 Use Narratives to Describe Needs
14. 14 As a developer I want to use CPU and memory resources So that I can deliver some business capability. #GHC19 Example: Core Compute
15. 15 As a developer I want to securely manage my secrets So that I can mitigate exposure to passwords. #GHC19 Example: Secrets Management
16. 16 #GHC19 CORE COMPUTE BUILD PIPELINES NETWORKING DATA PERSISTENCE WORKLOAD ORCHESTRATION OBSERVABILITY ARTIFACT REGISTRY EXTERNAL DEPENDENCIES (SAAS/DC) IDENTITY & ACCESS SECRETS MANAGEMENT VULNERABILITY MANAGEMENT Ecosystem Products and Journeys
17. 17 #GHC19 CORE COMPUTE BUILD PIPELINES NETWORKING DATA PERSISTENCE WORKLOAD ORCHESTRATION OBSERVABILITY ARTIFACT REGISTRY EXTERNAL DEPENDENCIES (SAAS/DC) IDENTITY & ACCESS SECRETS MANAGEMENT VULNERABILITY MANAGEMENT Ecosystem Products and Journeys PATH TO PRODUCTION (“Hello Customer” P2P) PATH TO REPAIR (“Hello Customer” P2R) PATH TO COMPLIANCE (“Hello Customer” P2C)
18. 1 8 As an infrastructure engineer... #GHC19
19. I WANT TO RECLAIM MY NIGHTS & WEEKENDS 19 #GHC19
20. 20 Neither! Learn infrastructure-as-code End goal: quickly deliver "Hello, Customer!" #GHC19 "Expert Developer" or "Hero Operator"?
21. 21 As a developer / infrastructure engineer I want to deliver my service / infrastructure in an automated way So that it is secure, compliant, and ready for my customer. #GHC19 Example: Deployment Pipeline
22. 22 #GHC19 Infrastructure Deployment Pipeline UNIT Check configurations Example: terraform plan BUILD Automation Example: terraform apply TEST Check integrations Example: pytest,inspec- gcp, awspec SECURE Check security conformance Example: scout2, g- scout MONITOR Check monitoring exists Example: pytest PERFORM Check performance Example: locust, pumba PROMOTE Ready for next environment Conformance Tests, can run asynchronously
23. 2 3 As an architect... #GHC19
24. I WANT TO CHAMPION THE ARCHITECTURE "-ILITIES" 24 #GHC19
25. 25 security 0 high vulnerabilities resiliency less than 1% error rate for new deployment auditability less than 90 days since last audit #GHC19 https://www.thoughtworks.com/insights/blog/fitness-function-driven-development Architecture Fitness Functions
26. services & applications business capability delivered in 26 #GHC19 delivered by business value delivered on infrastructure
27. 2 7 As a CxO... #GHC19
28. 28 #GHC19 A Balancing Act Evolvability Vendor Lock-In Build vs. Buy Autonomy Cost Fixed vs. On- Demand Capacity Compliance Complexity Vendor Management Global vs. Regional
29. 29 Mean Time to Recovery Deployment Failure Rate Deployment Frequency Lead Deployment Time The 4 Horsemen of the DevOp-ocalypse
30. 3 0 Where do we start? #GHC19
31. Team Structure? 31 #GHC19 As an organization... Capabilities Development? Executive Buy-In? Known Journey?
32. 32 #GHC19 As an individual... remember your customer experiment read examples re-purpose join/ build a community
33. Please remember to complete the session survey in the mobile app. THANK YOU YOU CAN FOLLOW US@ #GHC19 Paula Paul paula.paul@slalom.com @paulapaultweets Rosemary Wang rosemary@hashicorp.com @joatmon08