Dunno if you guys gives a shit but if you guys are bored like me atm you can watch all of the latest movies and series on InstaFlixxer. I've been binge watching with my brother for the last days =)
Great video thx for sharing. I have a question, let's say that in your example, videos had a param called type and I want to get a list of users who have video type = 'ABC'. How would my URL look like?
Thanks for watching videos.. You can always use query parameter but in your case you are combining two resource videos and users, you can create based on one of them EX: ..users/videos?type=ABC
A question, will resource like "friends list" and "posts" in a social app will be considered as a "store"? As those are managed by the user and a user can add/remove friends or posts on his own.
Hi again :) Does it make sense to have two sets of API endpoints, one set which is aimed at regular users of API that let to access to only one user's resources and mostly are nested under the " /users/{user-id}/" in which they must provide their user ID, means that they can access only to their own resources. And another set of admin related endpoints under the "/admins/" that let admins of API access to resources of all users. Is this a good approach? Regards
I have one query let's say we have database of 10 million movies and we expose movie name with endpoint "/api/movies" as we can see it's not good idea to return all 10 million names instead I implement pagination to it "/api/movies?startswith=32&pagesize=20" it works fine now but what if someone do this "/api/movies?startswith=1&pagesize=1000000" you can see it's too much data should I impose some limit to how much name user can request , if not suggest me what to do
In this article: www.kennethlange.com/7-tips-for-designing-a-better-rest-api/ in section 2-Use Subresources to Show Relationships the author proposed two different rules of thumb for showing relationships: "part of" and "belongs to" relation. I was considering using "belongs to" but not sure if it would be the best choice. I am interested to hear your idea about them and know which one you would suggest. Regards
23 minutes of video and other 30 minutes taking notes, thank you!
That's probably one of the best URI tutorials I've seen, thank you!
The best api design tutorial I have ever seen!
Excellent | Very good explanation | Crystal clear presentation! - Best URI/URL Tutorial ! 👏
I've never learned these rules but followed something like this from studying. Thank you for increasing my knowledge.
Thanks for watching videos, Keep learning, help us grow this developer community - Like, Share and Subscribe
This is a really great explanation and made it a lot clear for me on how to design my REST endpoints.
Thank you so much for sharing this :)
thanks for watching videos
Nice to capture everything in 23:39 min video. Easy and Best.
This was very well explained, thank you!
Excellent. Not nearly enough of this sort of more rigorous educational content in web development. Too much hackey thinking going around
Very Well Explained, I had learned new things. Thanks for sharing your knowledge
Thanks for watching videos.
Dunno if you guys gives a shit but if you guys are bored like me atm you can watch all of the latest movies and series on InstaFlixxer. I've been binge watching with my brother for the last days =)
This is an amazing one, 100%
excellent information and presented very neatly.
Very informative video. Keep up the great work!
Quality content.
Great video!! Thanks for publishing it!!
Excellent!! precise explanation.
Great class man I learned a lot, thank you!
super explination
Great video thx for sharing. I have a question, let's say that in your example, videos had a param called type and I want to get a list of users who have video type = 'ABC'.
How would my URL look like?
Thanks for watching videos..
You can always use query parameter but in your case you are combining two resource videos and users, you can create based on one of them EX: ..users/videos?type=ABC
Great
Good Explanation...!
Great!
Thanks for watching videos..
A question, will resource like "friends list" and "posts" in a social app will be considered as a "store"?
As those are managed by the user and a user can add/remove friends or posts on his own.
yes,
@@JRACADEMY Thank you so much for your response.
Hi again :)
Does it make sense to have two sets of API endpoints, one set which is aimed at regular users of API that let to access to only one user's resources and mostly are nested under the " /users/{user-id}/" in which they must provide their user ID, means that they can access only to their own resources. And another set of admin related endpoints under the "/admins/" that let admins of API access to resources of all users.
Is this a good approach?
Regards
Thanks for watching videos, that is also good approach, and there is no one good or bad approach, it is based on functionality of your application.
Can someone please tell me where can I find these ppt or notes in the videos??
I have one query
let's say we have database of 10 million movies and we expose movie name with endpoint "/api/movies"
as we can see it's not good idea to return all 10 million names instead I implement pagination to it
"/api/movies?startswith=32&pagesize=20" it works fine now
but what if someone do this
"/api/movies?startswith=1&pagesize=1000000" you can see it's too much data
should I impose some limit to how much name user can request , if not suggest me what to do
Can I know why call it URI even if it's the same as URL in this case
Thanks to provide a good video.. katalon studio API testing also doing . How to do it..
thanks for watching, Katalon Studio Testing, i will update you when we create video...
Awesome!
Awesome !!
as the video is full of information, may its better to split the video to be less than 10 minutes.
In this article: www.kennethlange.com/7-tips-for-designing-a-better-rest-api/ in section 2-Use Subresources to Show Relationships
the author proposed two different rules of thumb for showing relationships: "part of" and "belongs to" relation.
I was considering using "belongs to" but not sure if it would be the best choice. I am interested to hear your idea about them and know which one you would suggest.
Regards
Thanks for watching videos, yes, belong to is good approach...again cross check your apis with your functionality of application.