AtlasCamp 2016: Art of PaaS - Lessons learned running a platform for hundreds of microservices
0 likes586 views
The document presents insights from Robin Fernandes about running 'micros', a platform for microservices at Atlassian, emphasizing the importance of balancing consistency and flexibility in platform design. It outlines the key components of the platform, such as deployment processes and lessons learned regarding service management and architecture. Key recommendations include enforcing common practices while allowing for technology stack flexibility and resource isolation to support a healthy microservices ecosystem.
AtlasCamp 2016: Art of PaaS - Lessons learned running a platform for hundreds of microservices
- 1. ROBIN FERNANDES • MICROS TEAM LEAD • ATLASSIAN • @REWBS Art of PaaS: Lessons learned running “Micros”, a platform for hundreds of microservices
- 4. PaaS Overview CloudFormation RDS S3 DynamoDB EC2
- 5. Over services running right now 430
- 6. • Big cool statistic • 2,56 9 • Add-Ons in Marketplace Todo: better image Why do we need a Platform?
- 7. Data Centre JIRA & Confluence Cloud Architecture Rack Cloud instance in OpenVZ container
- 9. Breaking up the Monoliths * * Data Centre Rack BlobStore service PaaS
- 10. Breaking up the Monoliths > < Data Centre Rack PaaS _ _ - - /oo o o . .
- 11. The platform is set to grow PaaS
- 12. • Big cool statistic • 2,56 9 • Add-Ons in Marketplace Todo: better image What does the platform do?
- 13. + SD{ } Artifact Descriptor Deploying a Service
- 14. Deploying a Service name: Micros Workshop description: A sample app links: binary: type: npm artifactId: '@atlassian/micros-workshop' version: 0.0.1 healthcheck: uri: /healthcheck source: url: 'ssh://git@stash.atlassian.com/x.git' notifications: email: rfernandes@atlassian.com owners: - rfernandes@atlassian.com organization: Engineering Services
- 15. + SD{ } Artifact Descriptor https://<service>.atlassian.io Deploying a Service Compute: CloudFormation stack with: • Route 53 DNS record • Elastic Load Balancer • EC2 instances in Autoscaling group Resources: • S3, RDS, DynamoDB • Redis, Memcached, SQS…
- 17. . . cloudymccloudface.atlassian.io > micros service:deploy my-service -f service-descriptor.yml Deploying a Service
- 18. • Big cool statistic • 2,56 9 • Add-Ons in Marketplace Lessons learned: Balancing consistency & flexibility
- 19. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data
- 21. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data Enforce: Standard upgrade flow
- 23. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data Enforce: Standard upgrade flow Enforce: Limited set of persistent data stores
- 25. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data Enforce: Standard upgrade flow Enforce: Limited set of persistent data stores Encourage: Resource isolation
- 27. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data Enforce: Standard upgrade flow Enforce: Limited set of persistent data stores Enforce: Common service metadata & cost allocation Encourage: Resource isolation
- 28. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data Enforce: Standard upgrade flow Enforce: Limited set of persistent data stores Enforce: Restricted ssh access Enforce: Common service metadata & cost allocation Encourage: Resource isolation
- 29. Where to favor rules & consistency? Enforce: Common logging & monitoring infra Encourage: Structured log data Enforce: Standard upgrade flow Enforce: Limited set of persistent data stores Enforce: Statelessness & disposable compute nodes Enforce: Restricted ssh access Encourage: Resource isolation Enforce: Common service metadata & cost allocation
- 30. 12 Factor (not pets) Nodes as cattle (not pets)
- 31. Where to bend the rules / favor flexibility? Enable: Service-level technology stack flexibility
- 33. Where to bend the rules / favor flexibility? Enable: Service-level technology stack flexibility Enable: Integration with 3rd party services
- 34. Where to bend the rules / favor flexibility? Enable: Service-level technology stack flexibility Adapt to underlying platform limitations Enable: Integration with 3rd party services
- 35. Where to bend the rules / favor flexibility? Enable: Service-level technology stack flexibility Adapt: Education & on-boarding Adapt to underlying platform limitations Enable: Integration with 3rd party services
- 36. Where to bend the rules / favor flexibility? Enable: Service-level technology stack flexibility Adapt: Education & on-boarding Adapt to underlying platform limitations Enable: Integration with 3rd party services Open the platform for contributions
- 37. Contributions & Self-hosted PaaS components Bootstrapping Service Deployment orchestration service Chaos Monkey Log Analysis Service PaaS PaaS PaaS PaaS PaaS Simple Workflow integration Service cost estimation Data Pipelines Integration Service-to- service auth …
- 38. Where to bend the rules / favor flexibility? Enable: Service-level technology stack flexibility Adapt to underlying platform limitations Enable: Integration with 3rd party services Adapt: roadmap to inbound requests & technology trends Open the platform for contributions Adapt: Education & on-boarding
- 39. Organisation wide: Disaster Recovery Compliance Infra improvements: Container Clusters Serverless
- 40. Promises of Service Decomposition Choice of tech stacks Scalability Independent deployments Resilience End-to-end ownership Your platform should enable them – with heart and balance. PaaS
- 41. Healthy PaaS —> Happy Microservices! Balance consistency with flexibility Encourage / enforce “12 factor” & “nodes as cattle” Keep the barrier to entry low Tips for a healthy, balanced PaaS & a happy microservice ecosystem.
- 42. ROBIN FERNANDES • MICROS TEAM LEAD • ATLASSIAN • @REWBS Thank you!
- 43. Reuters. Chickens perch on the roof of a hennery to escape rising floodwaters after Typhoon Utor hit Maoming, Guangzhou province August 15, 2013. Typhoon Utor hit China's southern Guangdong and Guangxi provinces before easing to a tropical storm. Image Credits https://design.atlassian.com/ Courtesy of Scott Monday: - https://au.pinterest.com/pin/146085581635905884/ - http://scottmonday.com/ Copyright: velvetocean / 123RF Stock Photo – http://www.123rf.com/profile_velvetocean Copyright: feedough / 123RF Stock Photo – http:// www.123rf.com/profile_feedough' Copyright: iimages / 123RF Stock Photo – http:// www.123rf.com/iimages_feedough