How to support software development teams developing and operating with zero time-to-market and zero down-time? The deck gives a brief glimpse to Yle (The Finnish Broadcasting Company) tool chain and the way of developing and operating in public cloud. Transformation from own data center to public cloud based infrastructure can bring enormous benefits if done right. Infrastructure as code, continuous delivery and operations support tool set will greatly improve chances to redeem the promises. Gaining the cloud benefits fast but safe require a careful balance between enforcing good habits and providing support to make development teams thrive. The slides are from Finland AWS meetup on March 2016.

1. Supporting multiple
development teams
developing and operating with
zero time-to-market and
zero down-time.
Olli Vistbacka, Development Manager at Yle
Kalle Ylä-Anttila, Architect at Yle

2. Environment

3. 10+ CROSS-
FUNCTIONAL
TEAMS

4. UUTISVAHTI
AREENA
TUNNUS
UUTISET
URHEILU
Multiple Services
INTERNAL

5. More bang for
the buck with
good quality?
Problem #1

6. How to to enforce
basic infra-level
security?
Problem #2

7. Customer value =
Total effort -
overhead
Bang for the buck

8. 1. Duplicated work
2. Build and maintain
infrastructure
Overhead

9. Js
LOG
MON
VM
NET
HW
PUPPET
Before: Custom stacks
Js
LOG
MON
VM
NET
HW
PUPPET
Sca
LOG
MON
VM
NET
HW
PUPPET
Clj
LOG
MON
VM
NET
HW
PUPPET
Development team
Partner #1
Partner #2
Service #1 Service #2 Service #3 Service #4

10. Solution

11. Js
S#1
IMG
Docker
AWS
Now: Container-driven code-based Infrastructure
Sca
S#3
IMG
Clj
S#4
IMG
Yle AWS Tools
DevOps team
Service #1 Service #2 Service #3 Service #4
Js
S#2
IMG
OPS team
Legacy

12. https://spotifylabscom.files.wordpress.com/2014/03/spotify-engineering-culture-part1.jpeg
yle.fi OPS team supports
development teams
to use code-based
infrastructure.
OPS team supports development teams

13. https://spotifylabscom.files.wordpress.com/2014/09/spotify-engineering-culture-part2.jpeg
yle.fi development teams
have full autonomy inside
containers.
Only handful of techs and
tools are supported by
OPS team.
development teams have full autonomy

14. OPS team
members visit in
teams as OPS lead.
DevOps team

15. OPS team DevOps’es
code-based-infra,
legacy and tools.

16. As soon as available
in Region EU
Amazon ECR
Docker Hub
Amazon ECS
Development Flow

17. Amazon
RDS
Amazon
ElastiCache
Amazon
VPC
AWS IAM
SANE DEFAULTS
NewRelic POLICIES
NewRelic THRESHOLDS
Logging and monitoring
Amazon
Elasticsearch
Service
Amazon
SQS
Amazon
CloudWatch
Amazon ECS
TERRAFORM MODULES
Yle AWS Tools

18. Takeaways

19. Decide when to enforce
Remember goal: more bang for the buck!
rules < support devdev
AD
50%
Konsepti
75%
PO
75%
UX
50%
OPS
0%

20. Make the
securest way the
easiest way
by providing sane defaults and support
for the most common technologies used.