Platforms FTW!
This document discusses platforms and DevOps. It defines a platform as a service-oriented architecture combined with automation that provides speed, robustness, and scalability for developers. It discusses the benefits of platforms and provides examples like AWS, Heroku, Netflix OSS, and Cloud Foundry. It also recommends readings on platforms and DevOps. The document outlines the "Bezos Mandate" where all teams must communicate through service interfaces. It shares the author's experience building platforms at Hyatt and how platforms can provide core services and facilitate API development. It stresses that "DevOps" should not be in team names but may be appropriate in job titles and descriptions. In the end, it emphasizes that DevOps is difficult to define
Platforms FTW!
- 2. $ whoami • Developer • -> Architect • -> CTO
- 3. $ whoami -O RLY? • Developer • -> Architect • -> CTO
- 4. What is a Platform? Mise en place for developers
- 5. In slightly more technical terms… Service Oriented Architecture + Automation = Platform FTW!
- 6. Speed
- 7. Robustness
- 8. Scalability
- 10. Some Examples
- 11. AWS
- 12. Heroku
- 13. Netflix OSS
- 14. Cloud Foundry
- 18. Steve Yegge’s Google+ rant
- 19. The Bezos Mandate • All teams will henceforth expose their data and functionality through service interfaces. • Teams must communicate with each other through these interfaces. • There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. • It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn't matter. Bezos doesn't care. • All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. • Anyone who doesn't do this will be fired. • Thank you; have a nice day!
- 22. Heterogeneous Platform + Core Services
- 23. Hyatt circa 2010
- 26. API Gateway
- 27. API Gateway features • Presents a uniform API and a single ingress to all services • Routes to services based on dynamically configured URL path matching • https://api.hyatt.com/v1/…/…/ • Authenticates all requests using API keys • Performs rate limiting based on API key
- 28. Future Enhancements • Circuit breakers for robustness • API analytics using streaming analytics service • Aggregation and assembly of custom projections • Multi-tenancy and externalization? • Whatever else we discover based on customer feedback
- 30. Who ya gonna call?
- 31. DevOps Unicorns
- 32. What’s in a name? • Should ‘DevOps’ appear in a team name? NO! • Should ‘DevOps’ appear in a job title? Maybe • Should ‘DevOps’ appear in a job description? Absolutely. Search http://hyatt.jobs for some nice examples ;) • What is ‘DevOps’ anyway?
- 33. https://groups.google.com/forum/?fromgroups=#!topic/devops/u2KnDJ04xdw 55 posts by 31 authors in this thread alone
- 34. DevOps is like Porn You know it when you see it
- 38. Full Stack Developers source: http://happytesting.wordpress.com/2013/02/01/agile-testing-unicorn-perspective/
- 39. Questions? Please remember to evaluate via the GOTO Guide App