Building software.
WHAT THEY PROVIDE
Environments created and destroyed on demand Shared code repositories Automated build and deployment
WHY THEY SUIT DEVELOPMENT
Environments that match production No hardware to provision Costs only while running
WHAT TO CONTROL
Environments left running.
That is the most common source of waste.
WHAT TO DO
Shut down non-production environments outside working hours Tag everything, so ownership is clear Set spending limits on development accounts
WHAT TO SEPARATE
Development from production, entirely.
Different accounts where possible.
WHY
A mistake in development should not reach production or its data.
WHAT NEVER TO USE IN TESTING
Real customer data.
Use sample data instead.
WHAT TO SECURE
Code repositories, which frequently contain credentials by accident Access to production
WHAT TO CHECK
That no keys are committed to the repository.
WHAT TO AUTOMATE
Deployment, so it is repeatable and reversible.
