Deep Dive into REST API Design and Implementation Best Practices

[@shinyshark2247]

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.

[@jaredroder2842]

Maybe add an endpoint? GET /api/collection/count

[@ezwalduzumaki3161]

@@jaredroder2842 No, you would denormalize count. Another thing is using cursor based pagination, not offset. Offset means -> After X, give me 10. X being a number. You would still have to go through all the items. Better is cursor based like stripe. Explicitly saying after post_id, give me 10. Just need to make sure it's sorted.

[@DebapriyaMukherjee-y5y]

This is the best video I have came across after wasting time in so many craps.

[@abdulazeez.98]

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

[@SoftwareDeveloperDiaries]

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

[@collinskariuki7089]

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

[@gunnarliljas8459]

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]

Thanks for the feedback :)

[@cannabisanomaly]

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

[@gregloin3658]

very synthetic, complete and rich. the explanations are of quality. thank you very much

[@BABEENGINEER]

This vid is so soothing and informative!

[@SoftwareDeveloperDiaries]

Happy to hear you liked it! 🤓

[@itsfoss5268]

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

[@SoftwareDeveloperDiaries]

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

[@fb-gu2er]

Then your college sucks

[@erezbenkimon3899]

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

[@SoftwareDeveloperDiaries]

Thanks mate! ☺️

[@ExeeGamingYT]

Best video ever.!! Thank you brother❤

[@SoftwareDeveloperDiaries]

My pleasure 🤗

[@roopeshsingh3211]

Got Very Solid understanding of Rest API 🙌😄

[@SoftwareDeveloperDiaries]

Awesome! :)

[@vmmoorthi]

So helpful to understand the real world application architechture

[@prerakhere]

Excellent. Thanks!

[@abdelwahidbenzerrouk8271]

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.

[@SmartWizzard]

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]

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! :)

[@mravacado1587]

Versions can also be specified in the header

[@Other-stuff-sports-lm1ok]

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

[@SoftwareDeveloperDiaries]

Will do, thank you! 😊

[@juststudying1019]

Earned a new subscriber, thanks.

[@SoftwareDeveloperDiaries]

Happy to have you here! 😉

[@josh45000]

This video is one of the best

[@truechecker680]

I have question. Let's say, we have /api/towns endpoint and we have multiple PATCH actions on this endpoint like enable-town (change param isEnabled to true) etc... How can u operate on just one endpoint, when there are multiple PATCH actions? For this reason, I was using /api/towns/{id}/enable, /api/towns/{id}/change-tax-value but dunno if its best practice.

[@mariocortes2670]

Great explanation!

[@SmartWizzard]

This is excellent video exceptionally done

[@nihshrey]

This video is brilliant.

[@ricmorris9758]

Query APIs and REST APIs are different things with different challenges and solutions.

[@kennedymwenda3357]

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]

What exactly do you mean by the query level? 🙂

[@AnshulMarele-gbaa]

Hi, I have my Excel file which is updated through an odbc connection. But how can I sync/connect that Excel data into Google Sheets that could be updated automatically in periodic intervals. Any Solution? Thanks

[@javadmh7827]

Nice One 😍

[@ogagaDotTech]

Excellent

[@zartcolwing3218]

I disagree with what it is said 6:42 about the status code of idempotent verbs possibly being different depending on the situation on the server. IMHO, Idempotant verbs (GET, PUT DELETE) must always return the same code (in case of success) no matter if the operation was effectively performed or not otherwise the request is not idempotant anymore. For example, a DELETE should always return 204 no content, even when the resource did not exist to begin with (unless a serious error occurred while attempting to delete an existing resource - like a lock or a lack of permission). This decision is motivated by the fact that the effect of a DELETE is to remove a given resource. If the resource did not exist to begin with, the contract has been fulfilled, and this should not be passed on as an error. Returning a 404 not found, is a terrible idea, that forces the client to interpret two totally different return codes as success.

[@sidekick3rida]

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

[@SoftwareDeveloperDiaries]

Haha i guess so

[@nchaganlal]

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]

Thanks for the insight!

[@supa1009]

there are also action based APIs not only resource based

[@Christakxst]

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

[@gourabsarker9552]

Sir do you earn 100k euros a year as a software developer in Germany? Plz reply. Thanks a lot.

[@cariyaputta]

It's quite weird to directly ask stranger for their salary like this.