Rest API - Best Practices

Rest API - Best Practices - Design

Рет қаралды 98,976

Күн бұрын

Get a Free System Design Roadmap PDF with 145 pages by subscribing to our monthly newsletter: 1levelup.dev/roadmap
✏️📘 Summary Notes: 1levelup.dev/blog/consistent-...
0:00 - Introduction
0:52 - Stateless API
2:29 - Making Stateful Apps Stateless
4:37 - No action for the API
7:52 - Do not return plain text
9:35 - Recipe for disaster
12:38 - Handling Exceptions
14:26 - Worth to HATEOAS?

Пікірлер: 34

@luczztem 9 ай бұрын

I've never seen a so well made video about APIs, and I watch a LOT of coding related content! Congrats and thanks bro this one is a gem.

@MrChest001 8 ай бұрын

This video just made me to re-learn everything I know about Rest API

@awaitingforsunrise Жыл бұрын

Very useful and quite understandable. Very good quality. Thank you!

@collinskariuki7089 6 ай бұрын

Thank you so much for this. This video is very informative, straight to the point and so well done

@julienwickramatunga7338 8 ай бұрын

Very nicely explained, thanks a lot!

@DannyLearnsPega 11 ай бұрын

Great content. Straight to the point. :) If you don't mind me asking, what software do you use for your animations and texts?

@caiotrevisan6057 6 ай бұрын

I love the content I just wished it was louder hehe. Thx.

@RicardoSilvaTripcall 8 ай бұрын

Amazing explanation !!!

@CASLOAcademy 3 ай бұрын

Good stuff! Congrats and thank you

@kssaravo Жыл бұрын

Great Video. Thank you for your effort.

@EnavSounds 9 ай бұрын

Nice video. Like few nowadays short and to the point

@indian6755 Жыл бұрын

Your videos are very informative and awesome

@cherifabdelrahmen2376 Жыл бұрын

great video, thank you!!!

@markzuckerbread1865 9 ай бұрын

Helpful video, subbed!

@akashthoriya 9 ай бұрын

Great content

@ogunsanmidejiseye6037 Жыл бұрын

Great video has always. Can you design a core banking application? mainly how transfers, deposit and withdrawers work, for large scale bank app

@aliadel1723 6 ай бұрын

Awesome channel

@eudaimonia2120 Жыл бұрын

Excellent 😍

@adesh116 11 ай бұрын

Could you please expand on the uri naming section for real world scenarios.. i would like to know how to name apis for non crud operation ie what would your name your api that is used to upload or download a file, send out a notification or even login, signup, reset password for a user (as according to rest naming scheme /users/login isnt right as login is an action). This is something I see being missed by a lot of tutorials.

@t0nn1x 9 ай бұрын

I don't want to upset you, but these are all CRUD operations)

9 ай бұрын

It's been a while since your comment, but basically login, signin up, uploading a file could be described as different operations login (POST): You request your credentials to be processed on the server and as a response you get authorization credentials signup (POST): you send your data to register/create a new user besides that, it's not a good practice to send credentials, passwords, usernames as URI parameters given that those could be sniffed by some middle man upload a file (POST): api/files download a file (GET): api/files/{fileId] notifications: - global notification for all users POST: api/notifications - notifications for a given user: PUT: api/notifications/users/{userId} - get notifications GET: api/notifications (based on the logged user you give back their notifications) - reset password is a request to get something: usually as a POST, you send some data to be checked and used to get you a recovery pass or a recovery token or sth.