Spring Boot REST API Anti-Patterns and Best Practices

[@abdelrahman2348]

It would be amazing as well if you did best practice one with a similar great explanation

[@nareshn6628]

good content, thank you

[@momedalhouma14]

Thank you si a for the wonderful effort

[@Mr3dvinas]

Amazing thank you brother !!

[@mohamedshaker7528]

I've an enhancement on the pagination request you could use the one based index instead of subtracting to be zero by just providing the property on the application propertise spring: data: web: pageable: one-indexed-parameters: true

[@dishaarya3459]

Sir, kindly make the tutorial over Servlet JSP JDBC so that our prerequisites are clear.

[@zickzack987]

Only the first topic covers "Rest". Url naming patterns and certain status codes are not mandatory to be restful. Only a uniform interface.

[@nagkumar]

production-ready is also highly claimed too --> hence reworded as is the DONE #productEconomy scale ready

[@ajitnayak9t99]

Useful tutorial things!

[@universal4334]

Can i do a post for getting things if i have a nested hierarchy like a category inside multiple categories, then brand inside multiple brands, then size where I'll be having lot of sizes. So if i want to pass multiple categories, brands, and sizes to get info

[@sivalabs]

REST principles are more of guidelines than rules. Sometimes we have to use POST for getting the information due to the payload limitation of GET request. For example Elasticsearch uses POST for fetching matching documents.