A Connector, A Container and an API Walk into a Bar… Microservices Edition
Download as PPTX, PDF1 like1,058 views
The presentation discusses modern IT challenges and the importance of using integration, containers, and APIs to achieve agility in enterprise environments. It emphasizes building a cohesive infrastructure that prioritizes collaboration, automation, and adaptability in response to real-time changes. Key takeaways include the need for service discovery, automated CI/CD, and the value of open standards and open source solutions.
More Related Content
![[WSO2 API Day Chicago 2019] Sustainable Competitive Advantage](https://cdn.slidesharecdn.com/ss_thumbnails/wso2apidaychicago2019-sustainablecompetitiveadvantage-190626104303-thumbnail.jpg?width=560&fit=bounds)
![[WSO2 Integration Summit London 2019] An API-enabled Journey Towards Empoweri...](https://cdn.slidesharecdn.com/ss_thumbnails/wso2integrationsummitlondon2019anapienabledjourneytowardsempoweringtheworldwithknowledge-191108033935-thumbnail.jpg?width=560&fit=bounds)
![[apidays Live Australia] - Quantum Duality of “API as a business and a techno...](https://cdn.slidesharecdn.com/ss_thumbnails/asanka-2021-apidays-cdbata-auz-asanka-v1-210922090858-thumbnail.jpg?width=560&fit=bounds)
Similar to A Connector, A Container and an API Walk into a Bar… Microservices Edition (20)
A Connector, A Container and an API Walk into a Bar… Microservices Edition
- 1. A Connector, A Container and an API Walk into a Bar… Steven Willmott, Senior Director and Head of API Management Gluecon 2017 - 25th May, 2017
- 3. Who am I? Run API Infrastructure Business at Red Hat, Formerly CEO of 3scale Inc. Not talking about product. Come and see us at the Booth!
- 5. (Human) Containers at Scale?
- 11. In a mail room near you… You got Mail!
- 12. Why?
- 13. Common Modern IT Challenges Integrate SaaS Apps Customer and Partner Access Enable Customer Facing Apps via Many Channels Extend Legacy Apps IoT Devices and Architectures Data Access for Business Users
- 14. Success requires a Platform approach
- 15. Foundational Capabilities for Modern IT Integration APIsContainers
- 16. What do Enterprises Want?
- 17. a·gil·i·ty* /əˈjilədē/ noun “ability to move quickly and easily.” (*) lowercase‘a”
- 18. ?
- 19. Our Building Blocks do help… Integration Containers APIs
- 20. What about ‘A’ Agile?
- 21. Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 22. Code … SciLua : http://scilua.org/
- 23. Infrastructure code … Integrations Containers & Container Images APIs & API Definitions Routing & Failover Security PoliciesData Centers … Networking Infrastructure
- 24. Agile Manifesto Individuals and interactions => Focus on Teams and Interactions APIs, Pipelines, Traffic Patterns, Interdependencies are the new subject of discourse
- 25. Agile Manifesto Working software => 24/7 Infrastructure Rock solid deployment, testing and roll out processes, global coordination around Dev/Test/Prod
- 26. Agile Manifesto Customer collaboration => Alignment with overall business goals Company strategic and technical goals drive the roadmap, balance between short and long term goals
- 27. Agile Manifesto Responding to change => Capacity to respond to real-time change Having the capability adjust capacity, failover, combine APIs in different ways to react with speed
- 28. Captain Obvious?
- 29. • Codebase: One codebase tracked in revision control, many deploys • Dependencies: Explicitly declare and isolate dependencies • Configuration: Store configuration in the environment • Backing Services: Treat backing services as attached resources • Build, release, run: Strictly separate build and run stages • Processes: Execute the app as one or more stateless processes • Port binding: Export services via port binding • Concurrency: Scale out via the process model • Disposability: Maximize robustness with fast startup and graceful shutdown • Dev/prod parity: Keep development, staging, and production as similar as possible • Logs: Treat logs as event streams • Admin processes: Run admin/management tasks as one-off processes Focus on how to build a single (Micro)Service Example: 12 Factor Apps Heroku / 12 Factor App Model
- 30. Example: Death Star Diagrams Netflix – Circa 2012 Twitter– Circa 2013
- 31. What to do?
- 32. Four Areas…
- 33. Systems We Need Service Discovery Routing & Failover Fully Automated CICD Layered Reliable Identity End-to-End Testing Event Correlation & Observability
- 35. Open Standards & Open Source https://istio.io/https://openapi.org/ https://kubernetes.io/
- 36. Better Communication for Agile Collaboration Networking Infrastructure Integrations Containers & Container Images APIs & API Definitions Routing & Failover Security Policies Data Centers …
- 37. Take Aways…
- 38. ?
- 39. Go Beyond the Core Building Blocks Integration Containers APIs Teams and Interactions Working Infrastructure Collaboration Response To Change
- 40. Back in the Office… Find and connect with All the people in your Dependency chain Automate Just a Little Bit More
- 41. 41 Cloud Containers Microservices DevOps RED HAT BRINGS IT ALL TOGETHER Storage App Delivery Integration API Management