Deep Dive into REST API Design and Implementation Best Practices

Рет қаралды 40,731

11 ай бұрын

REST API best practices require effective REST API design and implementation that are often omitted in REST API tutorials for beginners. In this video, we're gonna go over important topics such as REST API endpoint naming, architecture, async operation, partial loading, error handling, security, HATEOAS, filtering, pagination, API versioning, and much more.
======⚡⚡⚡======
Consider supporting the channel by clicking the "Thanks" button ❤️
🙌 Become my Patreon and get exclusive perks: / softdevdiaries
💼 Follow me on LinkedIn and drop me a message if you'd like: / gusgadirov
💻 Also, let's connect on GitHub: github.com/gusgad
📚 Resources:
learn.microsoft.com/en-us/azu...
And don't forget to subscribe for more videos like this 😊

Пікірлер: 41

@collinskariuki7089 7 ай бұрын

I am currently learning about APIs and your video has been immensely helpful. Thank you so much for creating this content. I subscribed right away

@abdulazeez.98 11 ай бұрын

Awesome video. It’s really hard to find videos with such clarity and details on youtube. The animations are top notch 👌

@SoftwareDeveloperDiaries 11 ай бұрын

Thanks a ton! I felt like the animations are a bit rusty, so need to improve those maybe :)

@prerakhere 10 ай бұрын

Excellent. Thanks!

@gunnarliljas8459 10 ай бұрын

Wouldn't call it it a deep dive. More a wide dive. But, still, very good, An excellent introduction that could be starter for any API journey.

@SoftwareDeveloperDiaries 10 ай бұрын

Thanks for the feedback :)

@vmmoorthi 2 ай бұрын

So helpful to understand the real world application architechture

@mariocortes2670 7 ай бұрын

Great explanation!

@SmartWizzard 11 ай бұрын

This is excellent video exceptionally done

@shinyshark2247 3 ай бұрын

A warning for what is said at 5:43 - pagination does help performance by reducing the amount of records that are retrieved. If, however, you decide you want to include a property such as 'TotalItems' and use a count for that, be mindful of how you retrieve this count. In some scenarios, you might still be retrieving all the records you didn't want to retrieve.

@itsfoss5268 5 ай бұрын

I have learnt alot in 12 minutes than I did in a whole academic year for my CS degree. Cheers mate 🎉

@SoftwareDeveloperDiaries 5 ай бұрын

That's a great compliment, thanks a lot! :)

@fb-gu2er 3 ай бұрын

Then your college sucks

@BABEENGINEER 9 ай бұрын

This vid is so soothing and informative!

@SoftwareDeveloperDiaries 9 ай бұрын

Happy to hear you liked it! 🤓

@josh45000 10 ай бұрын

This video is one of the best

@ExeeGamingYT 11 ай бұрын

Best video ever.!! Thank you brother❤

@SoftwareDeveloperDiaries 11 ай бұрын

My pleasure 🤗

@nihshrey 2 ай бұрын

This video is brilliant.

@juststudying1019 9 ай бұрын

Earned a new subscriber, thanks.

@SoftwareDeveloperDiaries 9 ай бұрын

Happy to have you here! 😉

@erezbenkimon3899 4 ай бұрын

very good content dude. I will create a notebook from this video for future reference. keep going , you earned my subscription :)

@SoftwareDeveloperDiaries 4 ай бұрын

Thanks mate! ☺️

@roopeshsingh3211 10 ай бұрын

Got Very Solid understanding of Rest API 🙌😄

@SoftwareDeveloperDiaries 10 ай бұрын

Awesome! :)

@Other-stuff-sports-lm1ok 10 ай бұрын

great content! keep it going, you'll be the next big Tech youtuber

@SoftwareDeveloperDiaries 10 ай бұрын

Will do, thank you! 😊

@cannabisanomaly 2 ай бұрын

Just to clarify for anyone, at 5:58 the +author and -datePublished means that the author category will be sorted in an ascending order and datePublished will be sorted in a descending order

@abdelwahidbenzerrouk8271 5 ай бұрын

Good video, I would love to see how to deal with API Naming when you have some actions that are not representative by HTTP methods.

@kennedymwenda3357 9 ай бұрын

Would it not be the best to sort and order at the query level for API that you consume yourself e.g for a First Party SPA? Also please if can do a video on HATEOAS.

@SoftwareDeveloperDiaries 9 ай бұрын

What exactly do you mean by the query level? 🙂

@SmartWizzard 11 ай бұрын

From 7:05 it's getting confusing not because of words but lack of examples, can you please provide another video with examples that give details for all these requests, header responses, and response messages.

@SoftwareDeveloperDiaries 11 ай бұрын

Hey I won't be able to make a follow-up on that most likely, but I'd suggest checking out the page I linked in the description, you'll find all the needed examples there! :)

@supa1009 8 ай бұрын

there are also action based APIs not only resource based

@sidekick3rida 3 ай бұрын

Thanks, I learned a lot. But-how-are-hyphens-more_readable_than_underscores? Subjective, I guess.

@SoftwareDeveloperDiaries 3 ай бұрын

Haha i guess so

@Christakxst 7 ай бұрын

These things, OData got them right !But somehow, it's not so widespread...

@nchaganlal 2 ай бұрын

Adding version to endpoints and resources on their address/query strings leads to a brittle implementation.. always better to have API version and resource version on the HTTP headers. This will enable a better developer experience and less coupling between your microservices.

@SoftwareDeveloperDiaries 2 ай бұрын

Thanks for the insight!