The document discusses optimizing for speed in engineering, emphasizing the importance of quick decision-making and the role of continuous delivery versus continuous deployment in enhancing efficiency. It highlights the need for organizations to support engineering teams and manage system complexity through distributed architectures and operational tooling via PaaS. Additionally, it touches on key concepts like machine image configuration and desired state configuration in relation to orchestration in distributed environments.

1. Optimising For Speed

2. About
• Work for Paddy Power
• Predominately development
background
• Been leveraging CI since ~ 2003
• I haven’t written any books
• But…if I did, I would have
written…

3. • Because you want to win!
• By beating your competitors.
• By growing the market.
• By growing your market
share.
Why Optimise for Speed?

4. • Making decisions quickly.
• Building better, faster, lighter.
• Your organisation must exist to
support your engineering team.
• Replace human interaction
with API invocation.
How to Optimise for Speed

5. • Engineers own quality.
• You write it, your run it!
• Avoid moral hazard!
How to Optimise for Speed,
Safely

6. How to Optimise for Speed,
Safely
• Continuous Delivery vs Continuous Deployment
• Continuous Delivery requires manual promotion.
• Continuous Deployment is fully automated.
• Continuous Delivery is an opportunity to realise
efficiencies through convention.
• Continuous Delivery is realised through a staged
pipeline.

7. How to Optimise for Speed,
Safely
• Change the characteristics of the system complexity.
• Monolithic architectures centralise complexity.
• Distributed architectures distribute complexity.
• Manage distributed systems complexity with PaaS.
• Provide operational tooling through PaaS.

8. The Staged Delivery Pipeline

9. An Example Staged Delivery
Pipeline

10. The Code Commit Stage

11. The Build Stage

12. The Acceptance Test Stage

13. The Performance Test Stage

14. The Stability Test Stage

15. The Manual Test Stage

16. The Production Stage

17. AWord on Implementation

18. PaaS Maturity

19. PaaS from 30,000 Feet

20. PaaS from 30,000 Feet

21. PaaS from 30,000 Feet

22. PaaS from 30,000 Feet

23. PaaS from 30,000 Feet

24. PaaS from 30,000 Feet

25. PaaS from 30,000 Feet

26. Some Key Concepts

27. Machine Image

28. Configuration Management
• Control the functional and physical attributes of a
system.
• Desired state configuration allows you to declaratively
specify they system configuration.
• Convergence applies the desired state to the system.
• In distributed environments, Desired State
Configuration tooling requires orchestration.

29. Application Service

30. Application Blueprint

31. Environment Orchestration

32. Shared Services

33. –Kevin Kelly, co-founder of Wired Magazine
“The nature of an innovation is that it will arise at
a fringe where it can afford to become prevalent
enough to establish its usefulness without being
overwhelmed by the inertia of the orthodox
system.”

34. –Clay Shirky
“Institutions will try to preserve the problem to
which they are the solution.”

35. Thoughts?