DEV Community

loading...

Discussion on: Best RESTful API Practices and Tools

Collapse
dualyticalchemy profile image
⚫️ nothingness negates itself

you have not described REST but have confused HTTP to be synonymous with REST:

What needs to be done to make the REST architectural style clear on the notion that hypertext is a constraint? In other words, if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period. Is there some broken manual somewhere that needs to be fixed? (roy.gbiv.com/untangled/2008/rest-a...)

Collapse
adnanbabakan profile image
Adnan Babakan (he/him) Author

Thanks again for the information. I've updated the post and added this link for further studies in case anyone wanted to read.

Collapse
adnanbabakan profile image
Adnan Babakan (he/him) Author

Thanks for reading my article. As the title suggests I tend to explain some of the ways I like to organize my API server. Here I am not trying to explain how RESTful systems should be designed. Still thanks for the information.

Collapse
dualyticalchemy profile image
⚫️ nothingness negates itself

right on, but you raise the question: "What is RESTful?" and then subsequently give a definition that does not consider the constraints of REST or specifically HATEOAS.

you say:

"RESTful is an architectural style of designing an end-point in which software can retrieve data using the HTTP protocol."

this is an incomplete definition. as Roy fielding suggests, if you want to use a buzz word, stick with CRUD and HTTP, but you do not need to confuse the reader by mentioning REST if you are not interested in developing, describing, interpreting or explaining REST architectural style.

we want to focus on the essentials and allow developers to learn the right concepts

Thread Thread
adnanbabakan profile image
Adnan Babakan (he/him) Author

I have rephrased the sentence, thanks for helping me out. Tell me if I need to change to anything else. I'd appreciate it.