REST – the ignored parts – Webinar Recording
In a world dominated by APIs, where everyone seems to implement microservices with so many paradigms and standards to choose from, REST seems to be the default option. Despite that, many of these so-called REST APIs don’t respect the guidelines and become brittle by overlooking some of the most powerful constraints.
In this session, we will look over how we can design a REST API that is flexible and evolvable by being in sync with what HTTP has to offer.
We will look over OData as a way to filter data, versioning, hypermedia types specs, and status codes by fine-tuning .NET Core.
- 0:00 – Introduction
- 0:48 – Agenda
- 1:04 – What is REST?
- 4:51 – Uniform resource
- 8:53 – Manipulation of resources
- 9:16 – Self-descriptive messages
- 10:35 – Leverage the power of HTTP
- 15:19 – Status codes
- 20:10 – Verbs
- 21:02 – Describing errors
- 22:42 – ASP.NET Core web API
- 36:52 – Versioning
- 50:05 – HATEOAS (Hypermedia As The Engine Of Application State)
- 56:00 – Richardson Maturity Model
- 58:03 – Implementing parts in ASP.NET Core web API
- 1:04:26 – Summary
- 1:05:40 – Q&A
- Sample code used during the presentation (make sure to check the different branches)
- Irina’s blog and Twitter
About the presenter:
Microsoft MVP for Developer Technologies, Software Architect, and Microsoft Certified Trainer, always in a quest for latest trends and best practices in architecture, .NET, and the world around it.
Irina has more than 700 hours of delivered trainings, workshops, and presentations, being passionate about domain driven design and microservices with all their ups and downs. She is the founder of DotNet Iasi User Group where she tries to gather people that are willing to share their knowledge with others, and from time to time publishes articles on her blog.
Follow Irina on Twitter.