Cloud for Development and Test

Environments

Stuart Lynn

Chief Technology & Information Officer, Sage UKI

The 3rd largest ERP provider worldwide

6,000,000+ customers

13,000+ employees

26,500+ business partners

40,000+ accountant partners worldwide

38,000+ daily customer interactions

Source: Gartner, ERP Software Market

Share Top 10. Published March 2013.

Introducing Sage

Our AWS Journey

What's this

all about

then?

Early Investigation

Adhoc Usage

Skunk Works

Wider Adoption

Extended Use Cases

Cultivated Innovation

Production Systems

Process Automation

Business Critical

This could

be

interesting

Now we’re

getting

serious

Development

Confidence

Test UAT Production Pre-

Production

Development and Test Benefits

• No lead time on provisioning new machines.

• Simple to spin up new servers as needed and drop them when not

required.

• Easy to create multiple environments to run isolated versions of the

same application.

• Straightforward to integrate deployment to AWS within Team Build.

UAT Service Process

Continuous

Integration Server

Build

Code

Amazon S3 Storage

QA Team

Request code choice

Rightscale

Boots Amazon Instance

with code choice

Register

DNS

Records

Update UI with

URL to application

UAT Benefits

• The QA team are empowered to test what they want when they

want.

• If we get more QA staff testing concurrently there’s no impact on

service management for the infrastructure, we just start more

instances.

• ‘From Scratch’ provisioning for databases means each QA run is a

‘clean sheet’.

• 5 minute build time from new code being available to being able to

login to the provisioned application.

Final Takeaways

• Anyone creating some custom code, a bright idea, or a new planned

feature – can check out their code and provision it to a working

environment in minutes…

• The UAT boxes, will auto-destroy themselves after 12 hours to keep

the administration simple and costs sensible, or they can be

manually extended by 6 hours with a single click. The boxes can

also be manually destroyed if the code is no good, but this rarely

happens

Cloud for Development and Test

Environments

Stuart Lynn

Chief Technology & Information Officer, Sage UKI