Why API Ops is the Next Wave of DevOps
40 likes13,654 views
The document discusses APIOps, which merges API development with operations, drawing parallels with DevOps to emphasize collaboration and automation in software delivery. It highlights the evolution and significance of APIs in modern development, addressing the changing landscape and the need for rapid and reliable API lifecycles. The content also underscores the importance of best practices, tools, and standards in managing APIs effectively.
Why API Ops is the Next Wave of DevOps
- 15. People Gateways Debugging Support processes Testing processes Monitoring Rate limiting SecurityUsage patterns Tools Standards Design patterns APIOps:what’s different? Versioning Infrastructure Deprecation CI/CD
- 17. 1995 Why do we need a Web site? 2000 2005 2010 Of course we have a Web site Of course we have an API Why do we need an API?
- 18. 1995 Why do we need a Web site? 2000 2005 2010 Of course we have a Web site Of course we have an API Why do we need an API? Youarehere
- 21. A:Criticality APIs matter more now Alotmore…
- 35. Remember SOAP?
- 47. Whyallthetools?
- 51. TheAPILifecycle Requirements Design Development QA / Test Deployment Operations 1st generation API tools focused here But it turns-out now we need help elsewhere …
- 53. Backtospecs…
- 55. artifactsaregood
- 56. artifactsareglue
- 66. it’s CI/CDforAPIs Continuous Integration /Continuous Deployment (sameprinciples,samegoals)
- 71. We cannowuse APIsto: CreateAPIs Test APIs DeployAPIs Manage APIs MonitorAPIs
- 77. Dev Test / QA Prod / Ops APIs: Internal / External