Modernizing the Enterprise API Development Process
Download as PPTX, PDF0 likes326 views
The document discusses modernizing the enterprise API development process. It covers enterprise challenges like lack of communication and arbitrary deadlines. It then discusses using microservices and the idealistic versus pragmatic approaches. It recommends designing APIs first to gain better understanding and allow for collaboration. It also discusses tools for API design like SwaggerHub and integrating microservices through approaches like service meshes and API gateways, providing a demo of Kong.
Modernizing the Enterprise API Development Process
- 1. OUR JOURNEY MODERNIZING THE ENTERPRISE API DEVELOPMENT PROCESS
- 2. Introduction Travis Koenig Senior Director of App Exchange at RealPage Inc. Email – travis.Koenig@realpage.com
- 3. Enterprise Challenges Lack of communication Arbitrary deadlines Different tech stacks/skills Lack of documentation
- 5. Microservices Should I use microservices? Understand the benefits and the goal Understand the drawbacks
- 6. Microservices Idealistic approach small codebase (single responsibility principle) owns it’s own data independently deployable/scalable and testable fully decoupled (event driven)
- 8. Microservices Pragmatic approach Start bigger and continue to break down as you better understand domain lines Share a database if needed Shared host for services Service to Service communication
- 9. Microservices shared host and database
- 15. API Design First Why should I do design first? better understanding of the problem leading to a better design saves development time – errors, refactors, missing items collaboration parallel development faster feedback loop
- 17. Integrations How do I connect all this? point to point? service mesh? ( Istio, Linkerd, Kong ) API gateway ( apigee, Mashery, Kong, Tyk )