The document discusses best practices for building web APIs with ASP.NET Core 2.0, including using nouns not verbs in routes, being consistent in how data is retrieved and altered, using versioning to allow for changes over time, keeping implementations simple, using DTOs or simple models, validating models, and keeping controllers simple. It also mentions Azure API Management.

1. saturday 2017
ASP.NET CORE 2.0
WEB API
Emanuele Bartolesi
Microsoft MVP Visual Studio
and Development
Technologies
@kasuken
#VSSATPN

2. SPONSOR

3. LET’S START

4. NOUNS NOT VERBS
GET /getAllSchedules
GET /getAllSchedulesById
POST /createSchedule
PUT /updateSchedule
GET /schedules
GET /schedules/123
POST /schedules
PUT /schedules/123

5. BE CONSISTENT
Use GET to alter data
Return 404 for empty list
Don’t use status code
Use GET to get data
Use PUT/POST to alter data
Use status code correctly

6. USE VERSIONING
Business will change
Requirements will change
Change is inevitable
/api/v1/Schedules
/api/v2/Schedules
/api/v3/Schedules/123/Person

7. KISS – KEEP IT SIMPLE, STUPID
Don’t return more than you need
Don’t use much status code (200, 201,
404, 500)
Don’t write business logic in a controller
Keep your model simple
Document your API very well

8. USE DTO OR SIMPLE MODEL
DEMO

9. VALIDATE YOUR MODEL
DEMO

10. KEEP YOUR CONTROLLER SIMPLE
DEMO

11. AZURE API MANAGEMENT

12. Senior Full Stack Web Developer
and
Dragon Hunter Trainee
http://about.emanuelebartolesi.com http://blog.emanuelebartolesi.com
@kasuken
@kasuken emaueleb@outlook.com
//github.com/kasuken

13. THANK YOU!