DevOps
Download as PPTX, PDF1 like327 views
The document discusses DevOps practices at Lensa including: - Operations teams focusing on monitoring, logging, deployment automation, availability, and backups. - Building scalable, elastic, highly available systems requires non-trivial work. - DevOps means development and operations engineers work together throughout the entire service lifecycle from design to production support.
DevOps
- 3. Operations operations-focused problem areas: monitoring logging packaging, deployment automation availability backup
- 4. Operations Facts: A “Software as a Service” product has no value without deployment and operations Building scalable, elastic, H.A. systems is not a trivial task Shit will happen.
- 5. Prepare and Repair avoid single point of failures backup, monitoring, logging autoscaling self-healing services continous delivery with fast rollback option automation !
- 6. What is DevOps? DevOps means a lot of different things to different people because the discussion around it covers a lot of ground. DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.
- 7. Case Study: Amazon AWS 1. All teams will henceforth expose their data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. 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. 4. It doesn’t matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn’t matter. Bezos doesn’t care. 5. 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. 6. Anyone who doesn’t do this will be fired.
- 8. Case Study: Spotify “The lessons the DevOps movement has taught us are many, but one of the most important is the value of aligning the goals of Dev and Ops. Get them to work side-by-side, give them space to learn from each other.”
- 9. Case Study: Prezi running each product team like a “mini-startup” devops team → every team has devops engineers running on AWS(!)
- 10. Yes. SysAdmins?
- 11. DevOps at Lensa AWS Shared Responsibility Model every dev team: has AWS knowledge has the responsibility for their own services does operations on their own services …