GOTO Amsterdam 2015: A Cloud Infrastructure for Scaling Innovation Across Autonomous Teams
2 likes2,416 views
This document outlines Zalando's cloud infrastructure, aimed at fostering innovation across autonomous teams. It emphasizes the need for radical agility through principles of purpose, autonomy, and mastery, while detailing the technical architecture, including the use of AWS, microservices, and the deployment tool Stups. The platform enables efficient product delivery while ensuring compliance through robust tracking and auditing mechanisms.
![Pier One Docker Reg.
build
approve
EC2 Instances
Docker
Container
Application “myapp”
issue_management: Jira
Application Version “1.0”
artifact: docker/myart:1.0
Taupage AMI
Ticket System
Kio Application Registry
Ticket System
SCM
Image “docker/myart:1.0”
commit: afb123Issue “ABC-123”
spec: [...]
Commit “afb123”
msg: ABC-123..
✓ specs approved
✓ artifact tested
✓ artifact approved
STUPS: TRACEABILITY](https://image.slidesharecdn.com/2015-06-19gotoamsterdam-acloudinfrastructureforscalinginnovationacrossautonomousteams-150619111302-lva1-app6892/85/GOTO-Amsterdam-2015-A-Cloud-Infrastructure-for-Scaling-Innovation-Across-Autonomous-Teams-56-320.jpg)
GOTO Amsterdam 2015: A Cloud Infrastructure for Scaling Innovation Across Autonomous Teams
- 1. A Cloud Infrastructure for Scaling Innovation Across Autonomous Teams henning.jacobs@zalando.de / @try_except_ GOTO Amsterdam 2015
- 3. Henning Jacobs ● STUPS Hacker ● Twitter: @try_except_ ● henning.jacobs@zalando.de ABOUT ME
- 4. 15 countries 3 fulfillment centers 15+ million active customers 2.2+ billion € revenue 2014 130+ million visits per month 8.000+ employees ONE OF EUROPE’S LARGEST ONLINE FASHION RETAILERS Visit us: tech.zalando.com
- 9. A BRIEF HISTORY OF ZALANDO TECH
- 10. ZALANDO PLATFORM
- 11. ~70% of all applications WAR deployment Single deployment tool On-premise data center MAIN PRODUCTION STACK SINCE 2010
- 12. Platform THE CHALLENGE Platform team request servers deploy
- 13. Platform THE CHALLENGE 80+ delivery teams Platform team deploy request servers request storage
- 14. RADICAL AGILITY
- 15. GOAL DELIVER AMAZING PRODUCTS EFFICIENTLY AT SCALE, AND FEELING GREAT ABOUT IT.
- 16. 3 PRINCIPLES
- 17. PURPOSE
- 18. AUTONOMY
- 19. MASTERY
- 23. API FIRST
- 24. REST
- 25. SAAS
- 26. MICRO SERVICES
- 27. CLOUD
- 28. STUPS STUPS To Unleash Penguin Swarms
- 29. AWS STUPS DOCKER DEPLOY SSH ACCESS AUDIT REPORTS FULL AWS ACCESS A PLATFORM ON TOP OF AMAZON WEB SERVICES
- 30. AUTONOMY AND COMPLIANCE STUPS offers maximum freedom for developers while enabling near-real-time audit compliance for every single application.
- 31. One AWS account per Team Deployment with Docker Managed SSH Access REST/OAuth 2.0 mandatory Supports Traceability of Changes STUPS IN A NUTSHELL
- 32. Public Internet *.foo.example.org *.bar.example.org Team “Foo” Team “Bar”ELB ELB EC2 Instance EC2 InstanceEC2 InstanceEC2 Instance EC2 InstanceEC2 Instance Data Center LB EC2 InstanceEC2 InstanceLegacy Instances ISOLATED AWS ACCOUNTS
- 33. DEPLOYMENT
- 34. IMMUTABLE STACKS
- 35. AWS DEPLOYMENT WITH SENZA Senza CLI Pier One docker pull docker push Taupage
- 37. SENZA: BOOTSTRAP NEW CLOUD FORMATION STACK
- 39. LOGGING
- 40. APPLICATION LOGS: TAUPAGE SUPPORTS LOGENTRIES AND SCALYR
- 41. SSH ACCESS
- 42. SSH ACCESS: TIME-LIMITED ACCESS TO ANY TEAM SERVER
- 43. MONITORING
- 45. ZMON APPLIANCE *.foo.example.org *.bar.example.org Team “Foo” Team “Bar” EC2 Instance EC2 InstanceEC2 Instance EC2 Instance ZMON Appliance ZMON Appliance KairosDB EC2 Instance EC2 Instance ZMON Controller ELB ELB
- 46. HYSTRIX TURBINE
- 48. OAUTH
- 49. OAUTH: APPLICATION REGISTRATION IN YOUR TURN
- 50. OAUTH: CREDENTIAL DISTRIBUTION VIA S3 BUCKETS AWS YOUR TURN get access token Taupage Kio Mint OAuth Provider store passwords get password S3 rotate passwords
- 51. STUPS Frontpage http://stups.io STUPS Documentation http://docs.stups.io GitHub Repositories https://github.com/zalando-stups Trying out Senza and Taupage http://docs.stups.io/en/latest/user-guide/standalone-deployment.html LINKS
- 53. BACKUP
- 54. STUPS COMPONENTS
- 55. ● ELB for inbound traffic ● NAT instances for outbound ● HTTPS Only ● Internal subnets for app instances DMZ DMZ DMZ internalinternal eu-west-1a eu-west-1b eu-west-1c ELB EC2 internal EC2 NAT STUPS: AWS ACCOUNT VPC SETUP
- 56. Pier One Docker Reg. build approve EC2 Instances Docker Container Application “myapp” issue_management: Jira Application Version “1.0” artifact: docker/myart:1.0 Taupage AMI Ticket System Kio Application Registry Ticket System SCM Image “docker/myart:1.0” commit: afb123Issue “ABC-123” spec: [...] Commit “afb123” msg: ABC-123.. ✓ specs approved ✓ artifact tested ✓ artifact approved STUPS: TRACEABILITY
- 57. ZALANDO TECH CONSTITUTION PT. 1
- 58. ZALANDO TECH CONSTITUTION PT. 2