Why APIs Call for 2xs the DevOps
0 likes1,024 views
The document discusses APIs and DevOps practices. It begins by covering best practices for APIOps and how shifting to a microservices architecture can help teams develop and deploy applications faster. It then discusses how DevOps practices like continuous integration, delivery, infrastructure as code, and monitoring can benefit API development cycles by improving speed, security, collaboration, reliability and more. The document provides examples of how Amazon has shifted from monolithic to microservices approaches and emphasizes treating infrastructure like code and establishing automated pipelines with monitoring from the start.
Why APIs Call for 2xs the DevOps
- 1. © 2021, Amazon Web Services, Inc. or its Affiliates. Emmelyn Wang, Global Lead, DevOps AWS Marketplace Feb 3, 2021 APIs: 2xs the DevOps APIOps Track at Postman Galaxy
- 2. © 2021, Amazon Web Services, Inc. or its Affiliates. lifewingmate
- 3. © 2021, Amazon Web Services, Inc. or its Affiliates. lifewingmate Illustrator Luke Pearson @thatlukeperson
- 4. © 2021, Amazon Web Services, Inc. or its Affiliates. We’ll cover…. Best practices of APIOps and DevOps Why and how you go faster when you shift from monolithic to microservices architecture and how that relates to your DevOps practice You can try these practices today. Postman and Amazon API Gateway are integrated, for example.
- 5. © 2021, Amazon Web Services, Inc. or its Affiliates. Benefits of DevOps as APIOps Cycles Speed Security Business- oriented Improved Collaboration Rapid Delivery Faster Reliability Collaborative Scale Fits many needs Openly licensed Lean lifewingmate
- 6. © 2021, Amazon Web Services, Inc. or its Affiliates. Modern Application Development Automate and abstract away as much as possible so customers can focus on building applications for the business.
- 7. © 2021, Amazon Web Services, Inc. or its Affiliates. Requirement: Rapid innovation Innovation Flywheel Experiment Feedback Ideas
- 8. © 2021, Amazon Web Services, Inc. or its Affiliates. Drawn in my sketchbook
- 9. © 2021, Amazon Web Services, Inc. or its Affiliates. DevOps
- 10. © 2021, Amazon Web Services, Inc. or its Affiliates. Monolithic Application vs Microservices Build and deploy applications faster without straining additional resources • Does everything • Shared release pipeline • Rigid scaling • High impact of change • Hard to adopt new technologies • Does one thing • Independent deployments • Independent scaling • Small impact of change • Choice of technology Monolithic applications Microservices
- 11. © 2021, Amazon Web Services, Inc. or its Affiliates. Monolith Development Lifecycle developers release test build delivery pipeline app
- 12. © 2021, Amazon Web Services, Inc. or its Affiliates. Microservice Development Lifecycle developers delivery pipelines services release test build release test build release test build release test build release test build release test build
- 13. © 2021, Amazon Web Services, Inc. or its Affiliates. DevOps a Cultural Philosophy
- 14. © 2021, Amazon Web Services, Inc. or its Affiliates. DevOps Practices Communication & Collaboration Continuous Integration Continuous Delivery Infrastructure as Code Monitoring & Logging Microservices
- 15. © 2021, Amazon Web Services, Inc. or its Affiliates. 2001 Development transformation at Amazon 2009 monolithic application + teams microservices + 2 pizza teams
- 16. © 2021, Amazon Web Services, Inc. or its Affiliates. The biggest question we will get answered today is that when we talk about serverless, quite often we get asked “Can we follow the standard DevOps practices, development lifecycle that we used in traditional application development?”
- 17. © 2021, Amazon Web Services, Inc. or its Affiliates. The Development Lifecycle Learn Discover Prototype Author Test Debug Monitor Observe Diagnose Operate Deploy Use Case
- 18. © 2021, Amazon Web Services, Inc. or its Affiliates. Start right with three best practices 1. Treat your infrastructure the way you treat your code 2. Set up an automated integration and deployment pipeline 3. Build with monitoring and observability from day 1
- 19. © 2021, Amazon Web Services, Inc. or its Affiliates. API Security: Shared Responsibilities 1. If you don’t know what APIs you have how do you know what to secure? Observability and governance 2. Consider how you keep your API secure without duplicate and considering how your consumers will consume it
- 20. © 2021, Amazon Web Services, Inc. or its Affiliates.
- 21. © 2021, Amazon Web Services, Inc. or its Affiliates. 1662 4 5+
- 22. © 2021, Amazon Web Services, Inc. or its Affiliates.
- 23. © 2021, Amazon Web Services, Inc. or its Affiliates. Most Valuable Lessons for Architects Counterintuition produces architecture that considers how to handle trade offs better and up front
- 24. © 2021, Amazon Web Services, Inc. or its Affiliates. Most Valuable Lessons for Developers Coding the API isn’t just closing a ticket for sprint velocity. Now I have buy in to better serve those needs of the API Consumer.
- 25. © 2021, Amazon Web Services, Inc. or its Affiliates. Most Valuable Lessons for Product Leaders APIs, microservices, and even legacy SOA are not only technical concerns. Just DevOps and APIs Products cannot just involve business or technical stakeholders. In fact, you build on each others’ diverse strengths to build better APIs given your constraints.
- 26. © 2021, Amazon Web Services, Inc. or its Affiliates. Takeaways APIs as Product Start with what the consumer wants/needs before jumping to the solution Design 1st before you ever create a single line of code Litmus Test Can everyone upstream and downstream describe what the API does and why? How painful is it to document? KEY How delightful is it to consume with no internal knowledge?
- 27. © 2021, Amazon Web Services, Inc. or its Affiliates. Q&A Postman MC Emmelyn Wang, AWS Marketplace Somasundaram Subbu, AWS Marketplace