Express js api-versioning
Download as PPTX, PDF1 like274 views
The document outlines the implementation of API versioning using Express.js, detailing the transition from an old database architecture to a new one. It emphasizes the need for maintaining support for both old and new iOS builds while introducing new features solely in the v2 API. The document describes specific changes in request handling and outlines the creation of separate routes and controllers for v1 and v2 APIs.
1 of 10
Download to read offline
More Related Content
What's hot (19)
Ad
Viewers also liked (20)
Ad
Similar to Express js api-versioning (20)
More from DA-14 (11)
Express js api-versioning
- 1. Unnamed Project Original faults and profits
- 3. - New database architecture - iOS builds are not so easy to change - Old iOS build should be supported as well as new versions Why did we initiate API versioning?
- 4. ExpressJS: API versioning previous flow request middlewares responsecontroller model route
- 5. - New features should be implemented into API V2 - API V1 shouldn’t know about database changes - API V1 will not be updated with new features ExpressJS: API versioning requirements
- 6. ExpressJS: API versioning new flow to fit requirements request middlewares response controller V1 model route V1 route V2 controller V2 response service (mapper)
- 7. ExpressJS: API versioning new flow to fit requirements - response mapper origin url?response data process response emulate v1 response (map) response service / mapper /api/v1 /api/v2
- 8. - Create V1 and V2 routes - Move previous controller actions to V2 folder (controllers/v2) - Leave entities that should be changed in V1 - Convert / Migrate existing data to get it suitable with new database structure ExpressJS: API versioning new flow to fit requirements
- 9. Name: Roman Sachenko Email: roman.sachenko@gmail.com Skype: roman.sachenko
- 10. DA-14 2016