Skip to content

Instantly share code, notes, and snippets.

@cemeng
Last active November 16, 2017 00:29
Show Gist options
  • Save cemeng/1b78d37123bc29ddd5a4d8ea72e4d86b to your computer and use it in GitHub Desktop.
Save cemeng/1b78d37123bc29ddd5a4d8ea72e4d86b to your computer and use it in GitHub Desktop.
Build Best Practices and the Right Foundation for your First Production Workload
Get the correct people and roles
- small company one person w/ many hats
- need cloud skills - need to be leader
- need to be liasion between cloud vendor and business
Train these people
- there are classes offered by AWS - uhm okay
- holy grails - 5 AWS professional
- AWS Qwiklabs, youtube, acloudguru / udemy - even AWS people use these
- AWS Lunch & Learns -> find out about these
- or find these people through AWS partners
Culture
- You build it, you run it
- Good intentions are not enough
- Move decision making to the edges -> hence you build it you run it - decision means responsibilities
Foundational Processes & Mechanisms
- set up small, agile teams - 2 pizzas team rule
- work out KPI
- systematic metric based magamenent - use Cloudwatch for example - everything can be monitored in AWS.
use CludTrail
- bring dev and ops together
- revisit design
Processes & Culture Example
- Netflix - freedom of choice, automate everything
- other smaller examples Suncorp - leverage cloud to drive culture change
Design
- Design for Failure -> netflix with its simian army
- Component de-couple
- managed services
- scale & elasticity
- set up CI/CD pipeline - blue green deployment, a/b testing and all the jazz
- blue / green deployment - basically mean you have a blue environment and a green env
- you deploy to a blue env first - do smoke test there - if everything ok, then load balancer points to this blue env, if a rollback is needed, load balancer is changed to point back to the green.
Security
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment