Why APIs Call for 2xs the DevOps
summary
Shows concrete cases from three industries that double the DevOps cadence by adding an API Ops cycle to development: moving from monoliths to independently deployable microservices, automating pipelines and monitoring, and using a Postman + AWS integration (API Gateway) for testing and CI/CD. Includes outcomes: faster, smaller release cycles, a hackathon handoff that succeeded across tech stacks, published Dell Tech VantagePoint API docs that enabled real integrations and highlights compliance and PII handling.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 1:24Why APIs need 2x DevOps
- 2:28APIs as contracts and shared responsibility
- 4:12Modern app dev goals and innovation flywheel
- 7:02Monolithic vs microservices architectures
- 10:10DevOps evolution and two-pizza teams
- 12:22Best practices for API and DevOps
- 13:45What is API Ops methodology
- 15:30API Ops for architects developers and leaders
- 17:39Key takeaways and litmus tests
- 19:05Q&A session with experts
related talks
29mAccelerate API Innovation: Secrets to Staying Ahead
57mBring the API culture to DevOps teams
35mRoad to Efficient and Data-Driven DevOps
05mDevOps at
19mAvoiding the 8 Wastes of Lean API Development with OpenAPI & APIOps.
27mThe API Trends and Beyond
26mHow to accelerate channel delivery with APIs
25mAPIOps: automating API operations for speed and quality at scale