The Right Way To Build REST APIs

preview_player
Показать описание
Best Practices for building REST APIs.

💬 Topics:
1. Richardson Maturity Model;
2. Stateless vs Stateful APIs;
3. Define correct REST Endpoints;
4. REST Endpoints responses;
5. Plain Text vs JSON vs XML vs YAML;
6. Handling exceptions in APIs;
7. REST API versioning;
8. HATEOAS
9. The HTTP protocol;

Рекомендации по теме
Комментарии
Автор

I've been trying to learn API dev for a while now and this is the simplest and most crystal-clear video I've ever stumbled upon. Thanks a lot!

lucaruana
Автор

Personal opinion: a restful endpoint should be or something along those lines. The path should only refer to resources by name or identifier, since active items returns a subset of a specific resource it should be used in the query string since it is a filter. Also, according to the spec, PUT is for upserting not only updating. PATCH is for updates only

vexxxG
Автор

The only words that i have heard today that make sense have come from this video...Greatly appreciated.

jaimieomondi
Автор

The classical music in the background was soothing. The content was useful, thanks for sharing.

fadhilinjagi
Автор

So much value in this video, amazing!

louispetrik
Автор

Fantastic. Concise, useful illustrations, and I like the way you built the concepts up layer by layer. I'm a new subscriber.

mikec
Автор

Awesome, thanks! I thought you were gonna squeeze it into a 3 minute video but I was pleasantly surprised to see it go on until I checked the video length 😅

siya.abc
Автор

Thanks, this was very concise and helpful.

jamie_SF
Автор

Відмінне пояснення і анімація. Заслуговуєш на більше підписників!

TheDeluxeman
Автор

I recently quit web dev but i still come here watching cuz its interesting, and to like

cslearn
Автор

Awesome content! The knit pickers here can jump in a lake. It’s so hard to find actual production grade info like this! Chapeau 😊

maguilecutty
Автор

Great video. Just note REST isn’t the *only* option. RPCs can be great for internal API calls

bone_broth_
Автор

HATEOAS maturity can be achieved by returning HTML instead of JSON. Then the client can parse the response or pick a part that is interesting like the url for example.

MarcoDamaceno
Автор

The representation of backend and frontend developers is spot on

em
Автор

This was so clear and on point

Next, please do GraphQL

ChichaGad
Автор

Great video! Really clear explanation.

SuperKavv
Автор

7:08 RESTful APIs can return HTML too! Like HTMX suggests, there is nothing more HATETOAS than HTML with its natural support for links and forms etc

brnto
Автор

Would be interesting to see a video on event-driven architecture as well 🙏

JustMax
Автор

Awsome video man. Keep up the good work!

zorbak
Автор

My preference would be to have a query parameter of status = active instead of putting active in the URL

koenv