3. THE IRON AGE
"Infrastructure growth was limited by the hardware
purchasing cycle. Since it could take weeks for a new server
to arrive, there was little pressure to rapidly install and
con gure an operating system on it" -- Kief Morris
5. THE IRON AGE
Software development built around boxed software New
versions being released once a year, or less.
Expensive and time consuming release processes: build
everything, then test everything, then release
THE CLOUD AGE
Agile teams release changes frequently, often several times
a week
Expensive and time consuming release processes can’t be
used without grinding deployments to a halt.
Continuous delivery.
6. CONTINUOUS DELIVERY
Teams that employ continuous delivery have a ”deployment
pipeline”, a set of validations through which new version of
software must pass on its way to production. The pipeline has
different stages, each of which have their own environments
where the software can run.
7.
8. INFRASTRUCTURE AS CODE
As the number of services that teams operate grows, it
becomes unmanageable to maintain each one by pointing and
clicking through the UI. "Infrastructure as Code" is an
approach to deal with this issue. Con guration of each
service is automated, and the code and con guration is
stored with the source code for the application in version
control.
9. PIPELINES & WORKFLOWS
A further challenge for content management is that there are
two lifecycles happening at the same time, both requiring
authoring, veri cation, and release. One is the software
deployment pipeline, the other is the content creation
work ow. While software developers are authoring and
releasing software versions, content creators are at the same
time authoring and releasing content.
10.
11. MIGRATIONS
Migrate a space from an older content model
Modify existing entries so that they are valid according to
the current model.
Tests that verify that the current software works with the
current content model and latest content.
12.
13. CMS AS CODE
Content Model change move up the pipelin
Content Model should be stored with code.
Content, when needed, moves down the pipeline
Migration scripts migrate content models and
content
14. CMS platforms commonly used today don't work well for
agile development practices such as Infrastructure as Code
and Continuous Delivery.
Provisioning, migrating and testing Monolithic platforms is
dif cult to automate.