"ExpressJS - Disposable Hero" 1. Clean Controller 2. API versioning "Useful Tools...And Justice for All" 1. Data Analysis Tools - short review 2. Continuous Integration Systems 3. Rest Clients

1. Unnamed Project
Original faults and profits

2. ExpressJS: API versioning

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