I don't think that endpoint api/v1/cars/users/{userId} follows the REST semantics. The operation looks like filtration "give me the cars of the user with id = x" - so fo this purposes query parameters work well. So the proper way of implementing this endpoint will be GET api/v1/cars?userId=xxx Regarding export operations, just use headers to specify content you want. For example GET /invoices/123 produce by default JSON object, by if we use content type and accept headers to specify that caller needs application/pdf the response will be returned as PDF file with invoice details
You should use them when you want to transfer an entity to user, because transfering entities directly means that you load all data from DB, including @OneToMany, @ManyToOne relationships
Hi alibou, can you make the frontend part of your JWT code, with react or angular, preferably react, your tutorial was very helpful to me, but i would like a frontend to understand it better
Lol these look like some of the endpoints on the project I'm working on at my job. I've tried to raise the flag. The whole code base is littered with terrible conventions but no one else seems to care
/v1/api/products, but when it comes to aws api gateway, this gives the error, the aws api gateway expect /v1,/v1/api, and /v1/api/products a separate endpoints and expect a swager definition for each.....
I have a question about the content. Let's suppose you want to have a system which provides open access to anyone on the platform (e.g. unpaid customers) and 'secured' access to paid customers - what would the recommended naming convention be for good REST semantics? Thanks again for the content Nelson!
I would suggest not including that distinction in the endpoint names. For example, you could have GET /books be open access and POST /books require authentication. Just name your endpoints based on what the resources are.
you can configurate the requestMapping in your appication.propreties like that "server.servlet.context-path=/api/v1" after that when you use your and point you just ahave to gave him the name of your implementation .
It's api versioning. In this case, it is called URL segment versioning. But it can be done in other ways too. In general, when you have multiple versions of API, the clients need a way to tell you which version they want to use.
Hey, guys. I want to create good endpoints. So I have one question for all of you. How do you design your endpoint when you want to POST multiple pieces of content in one request?
If it makes you feel better, that's an actual person who goes by "Welven Da Great" and not a racist caricature. It must make you feel big claiming another person's appearance portrays racism. Do you shout and holler when you see a person with disabilities on ads?
@@AngelOfDeath943 Ik it's going to save for a POST request. My question was more towards the naming conventions. I'd argue saving something to a database should always to intentional, and using the save/ seems like a better name rather than just leaving it empty and just relying on POST method
@@Sahil-a-vim-user save is implied from post. because post means you are inserting. you dont need to add get/save naming to the route because POST/GET implies the behaviour. if you do both you are convoluting already defined behaviour.
The post verb tells you it's going to save. If you use a get it tells you it's gonna get something. If you use delete it tells you it's gonna delete something
I've purchased your course and found them really useful - keep up the unbelievable work! Thanks for the continuous content amigo!
We need that video! API design best practices
I don't think that endpoint api/v1/cars/users/{userId} follows the REST semantics. The operation looks like filtration "give me the cars of the user with id = x" - so fo this purposes query parameters work well. So the proper way of implementing this endpoint will be GET api/v1/cars?userId=xxx
Regarding export operations, just use headers to specify content you want. For example GET /invoices/123 produce by default JSON object, by if we use content type and accept headers to specify that caller needs application/pdf the response will be returned as PDF file with invoice details
You should make a video about DTO's and when to use then! Would help a lot.
It's not rocket science just google it if you really don't know
you should use them when you want to transfer data via an object
You should use them when you want to transfer an entity to user, because transfering entities directly means that you load all data from DB, including @OneToMany, @ManyToOne relationships
thanks! i was literally gonna do some research into endpoints for spring boot today and saw you uploaded this today.
Hi alibou, can you make the frontend part of your JWT code, with react or angular, preferably react, your tutorial was very helpful to me, but i would like a frontend to understand it better
Lol these look like some of the endpoints on the project I'm working on at my job. I've tried to raise the flag. The whole code base is littered with terrible conventions but no one else seems to care
time to find another job then, good luck
@@angelsv yep. Just got off of LinkedIn lol
/v1/api/products, but when it comes to aws api gateway, this gives the error, the aws api gateway expect /v1,/v1/api, and /v1/api/products a separate endpoints and expect a swager definition for each.....
So maybe it is good time to change company/project?
@@ArekTheBoss yes I'm working on it. Market is kinda slow right now and probably very saturated
Great video! Good examples. Looking forwards to an API design best practices video!
hola Amigo
very excited for the API design video!
I have a question about the content. Let's suppose you want to have a system which provides open access to anyone on the platform (e.g. unpaid customers) and 'secured' access to paid customers - what would the recommended naming convention be for good REST semantics?
Thanks again for the content Nelson!
I would suggest not including that distinction in the endpoint names. For example, you could have GET /books be open access and POST /books require authentication. Just name your endpoints based on what the resources are.
@Amigoscode please can you make a tutorial on OpenAPI (Swagger versioning) with Spring Boot
you can configurate the requestMapping in your appication.propreties like that "server.servlet.context-path=/api/v1" after that when you use your and point you just ahave to gave him the name of your implementation .
thanks, I had same endpoints in my app (it's running on production btw), it made me laugh, also good lesson :)
Hi Nelson! Could you make a video on hexagonal architecture?
that was awsome, waiting .. for REST design Best Practice video
considering taking Java from your master class, but have this mentality that its hard.
great code review!
Love this video convention, Thanks ;)
Great video! Thanks!
Aka muxlisizmiz videolariz zo'r!
Keep up the good work!
Hi Nelson, in the next video can you also mention versioning practices for apis in spring boot please.
Please vedio about serving file in spring boot with file system
Thank you we are waiting for api design best practice
Wow! That video i need ♥
It also unsecure to use entities to bind request direclty.
Hi Nelson, is it better to inject Repository or Service in another service class (to avoid circular injection)?
Go for Repository. No need to inject more logic then you need it.
@@erickjhormanromero6905 thanks man
i like your intellij theme, what is the name of your theme?
It's the new intellij update, you can find it in there
Bro please can you do your day in the life?
Can u kindly make a vdo on white label error router to methods so that any responseEntity be sent
I love this hat!
why developers use addresses like "api/v1" ? In most projects from github and in tutorials I see addresses like it
It's api versioning. In this case, it is called URL segment versioning. But it can be done in other ways too. In general, when you have multiple versions of API, the clients need a way to tell you which version they want to use.
The intro music lol.
Assalamu Alaykum, Take a video about solve problems, please??:))
👌!! Thanks!!
i will wait best api practics
Hey, guys. I want to create good endpoints. So I have one question for all of you. How do you design your endpoint when you want to POST multiple pieces of content in one request?
What is the content?
@@amigoscode For example, when there is a Student API, I want to post multiple contents called students. sorry i'm not good at english
good stuff
Are you using Fleet, aren't you?
no, new UI intellij, Settings -> appearance & Beahavior -> New UI
👍
I literally smashed the like button. Now I can't like again.
561st...Thanks
Dude why would you play into stereotypes with that thumbnail picture ? How's this racist characture relevant to your channel...SMDH!? 🙄
If it makes you feel better, that's an actual person who goes by "Welven Da Great" and not a racist caricature. It must make you feel big claiming another person's appearance portrays racism. Do you shout and holler when you see a person with disabilities on ads?
Good video, keep it up!
Selamun Aleyküm Cemaati Müslimin
Selamun Aleyküm
I don't understand some of the edits you made. api/v1/cars/save seems like a more informative name rather than just a POST request on api/v1/cars.
it’s POST, so its gonna save obviously
@@AngelOfDeath943 Ik it's going to save for a POST request. My question was more towards the naming conventions. I'd argue saving something to a database should always to intentional, and using the save/ seems like a better name rather than just leaving it empty and just relying on POST method
@@Sahil-a-vim-user save is implied from post. because post means you are inserting. you dont need to add get/save naming to the route because POST/GET implies the behaviour. if you do both you are convoluting already defined behaviour.
The post verb tells you it's going to save. If you use a get it tells you it's gonna get something. If you use delete it tells you it's gonna delete something
Don't bother wasting time on stuff like this. It doesn't matter unless you are building public API that obey by the RESTful standard
Great video, thank you!