This document summarizes a presentation on architecting for continuous delivery. It discusses what continuous delivery is, the importance of deployability and testability, and how microservices can help enable continuous delivery. Microservices make the system easier to build, test and maintain through better encapsulation and lower coupling. They also allow independent deployment of components and enable collaboration between teams. The document notes that organizations and systems should have structures that match, and that one team per service is an effective model. It emphasizes that operations at scale require resilience, security, and the ability to deploy reliably to unreliable platforms.

1. @jezhumble
innotech austin | 8 october 2015
architecting for continuous delivery

2. microservices

3. what is continuous delivery?
The ability to get changes—features,
configuration changes, bug fixes,
experiments—into production or into
the hands of users safely and quickly in
a sustainable way.

4. golden rules
software (trunk) is always deployable
everyone is checking into trunk daily
(at least)

5. configuration management
continuous integration
automated testing
ingredients

6. deployment pipeline

7. to validate golden rules
testability
“works on my machine”
actually means something useful
deployability
deployment is a low-risk,
pushbutton affair

8. microservices

9. internet architecture
“Operations at web
scale is the ability to
consistently create and
deploy reliable software
to an unreliable platform
that scales horizontally.”
Jesse Robbins, “Master of Disaster” @ Amazon| @jesserobbins | http://oreil.ly/1HRKUVE

10. make system easier to build and test
part of your system that could be swapped out for
another implementation
make system more maintainable (better
encapsulation, lower coupling)
enable collaboration
component / service

11. conway’s law
“organizations which design systems ... are
constrained to produce designs which are
copies of the communication structures of
these organizations.”
—Melvin Conway

12. conway’s law
“If you don’t want your product to look like
your organization, change your
organization or change your product.”
—Rebecca Parsons

13. one team per service
API
API
API
API

14. Bind Components at Run Time (μS)
“Transforming Software Development” | Ken Exner | http://bit.ly/1HxCEZy
API versioning
Independent deployment
Don’t break downstream!
Monitoring

15. Bind Components at Build Time
“Large Scale Continuous Testing in the Cloud” | John Penix | http://bit.ly/1BYMf70

16. Unreliable Platform
Resilience, security,
scalability, availability
deployability, testability
are architectural concerns.

17. Steve Yegge’s Platform Rant | http://bit.ly/1zxknpR

18. You build it,
You run it
Werner Vogels, CTO, Amazon | http://bit.ly/11UJjmN

19. http://www.flickr.com/photos/trustedsource/6132507962/

20. Strangler Application

21. questions
@jezhumble | jez@jezhumble.net
http://jezhumble.com/
© 2015 Jez Humble & Associates LLC