APIOps (C-level version)

Transcript

1. APIOps - Better processes for even better APIs 1
2. APIOps? 2
3. DevOps 3
4. broad concept with goals 4
5. improve collaboration between development and operations 5
6. improve deployment frequency 6
7. achieve faster time to market 7
8. lower failure rate of new releases 8
9. shorten lead time between fixes 9
10. improve mean time to recovery 10
11. CALMS Model 11
12. Collaboration 12
13. Automation 13
14. Lean Principles and Processes 14
15. Measurement 15
16. Sharing 16
17. GITOps 17
18. Attempting a defintion 18
19. System development / management pattern 19
20. GIT as the single source of truth 20
21. GIT as the single place where all operational tasks for all environments happend - create - change - destroy 21
22. All changes are observable / verifiable 22
23. Continuous Integration & Deployment 23
24. Standard Software Development Lifecycle 24
25. API Producer Lifecycle 25
26. API First 26
27. Open API 27
28. 28 Open API
29. Open API Extensions x-...-... 29
30. EVERYTHING as Code 30
31. EVERYTHING with the Code 31
32. Configuration as Code 32
33. Policy as Code 33
34. Policy as Code 34 - cloud native - compliance - validating infrastructure - best practices as polices - cost control
35. => APIOps 35
36. APIOps with Kong 36
37. 37 APIOps with Kong - Spec-first API Design using Insomnia Designer - Transform Spec to Kong declarative configuration Deploy configuration to environments Adjust configuration to specific needs per environment
38. codecentric AG Hochstr. 11 42697 Solingen Daniel Kocot Senior Solutions Architect daniel.kocot@codecentric.de www.codecentric.de Innovative - Trustful - Competent - Pragmatic 38
39. 39 References: title slide: Sliver linings, https:/ /www.flickr.com/photos/shivashenoy/