Over the last year, a team of software engineers have been quietly revamping the architecture, codebase and development practises at World Vision Australia. They have been using the principles of continuous delivery to deliver a SOA based IT platform for a non-profit who's business genuinely has a world wide impact. In the span of 6 months they have delivered several drops to production through a push button deployment process. We use Nuget, ProGet, WinRM, Chocolately, NSpec, Jasmine/Karma/PhantomJS and SpecFlow/Selenium/WebDriver. We test our deployment scripts with Canary deployments orchestrated through PowerShell. More interestingly we're using Puppet and Node.js to drive the idea of shipping products intended for single tenant architectures and the principle of "the machine as the artefact of the pipeline".

1. TOWARDS
A
RESPONSIVE
BUSINESS
The
Developer
Way

2. @nigelfds
github.com/nigelfds

6. Understanding
the problems

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

17. Different speeds
of evolution

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

27. Dealing with artifacts…

28. Managing Pipelines

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

46. ApplicaOon
Environment
Infrastructure

47. Build
Farm
S3
Bucket
Nigel’s
Laptop
Puppet
&
AWS
scripts
Cloud
FormaOon
APIs
Packaged
Scripts
Create
Machine
Self
Configured
Behind
the
scenes

48. Repeatable
&
ConOnuous

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.