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.
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
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.
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.
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.
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! :)
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
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.
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.
Maybe add an endpoint? GET /api/collection/count
This is the best video I have came across after wasting time in so many craps.
Awesome video. It’s really hard to find videos with such clarity and details on youtube. The animations are top notch 👌
Thanks a ton! I felt like the animations are a bit rusty, so need to improve those maybe :)
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
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.
Thanks for the feedback :)
I have learnt alot in 12 minutes than I did in a whole academic year for my CS degree. Cheers mate 🎉
That's a great compliment, thanks a lot! :)
Then your college sucks
This vid is so soothing and informative!
Happy to hear you liked it! 🤓
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
So helpful to understand the real world application architechture
very good content dude. I will create a notebook from this video for future reference.
keep going , you earned my subscription :)
Thanks mate! ☺️
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.
Best video ever.!! Thank you brother❤
My pleasure 🤗
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.
Got Very Solid understanding of Rest API 🙌😄
Awesome! :)
Versions can also be specified in the header
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.
What exactly do you mean by the query level? 🙂
Excellent. Thanks!
This video is one of the best
Earned a new subscriber, thanks.
Happy to have you here! 😉
This is excellent video exceptionally done
This video is brilliant.
Great explanation!
great content! keep it going, you'll be the next big Tech youtuber
Will do, thank you! 😊
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.
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! :)
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
Excellent
Nice One 😍
Thanks, I learned a lot. But-how-are-hyphens-more_readable_than_underscores? Subjective, I guess.
Haha i guess so
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.
Thanks for the insight!
there are also action based APIs not only resource based
These things, OData got them right !But somehow, it's not so widespread...
Sir do you earn 100k euros a year as a software developer in Germany? Plz reply. Thanks a lot.
It's quite weird to directly ask stranger for their salary like this.