CODEWITHSUNDEEP
rest
Anupam
Anupam

Reputation: 201

Why REST API method name important? Because I can use any of those method to perform CRUD operation

In REST full API has some method name like (GET, PUT, POST etc.) for some specific operation (CRUD) But I can perform any operation using any of the methods

Example for DB operations:

  1. I can create or insert a new document or delete or update using GET method.

  2. I can post or update or delete using POST method.

  3. I can delete or update or delete using PUT method.

    the same way I can use any of this method to perform DB (CRUD) operation

So, Why need this method to specify when we call any rest full API?

Upvotes: 0

Views: 775

Answers (2)

John H
John H

Reputation: 14655

To expand on Matías's answer, you have to think about the consequences of allowing consumers to call your API using any verb they wanted.

Firstly, your implementation is going to be more complex if you never know what operation is going to be expected. For example, if someone can update a resource using GET, how do you tell the difference between a query and an update? The answer: extra (needless) complexity of the implementation.

Secondly, there are consequences from the point-of-view of performance and scalability. GET allows easy caching of resource representations because of its idempotent nature - which is the expected convention. By not making it clear which verbs do what, you're making it harder to utilise strategies such as caching, which makes your API harder to scale.

Thirdly, it makes things more complicated for consumers. HTTP's convention-based approach is widely understood. Working with an API that doesn't follow that convention - especially one that labels itself as using HTTP/REST - is going to increase integration costs.

Upvotes: 0

Matías Fidemraizer
Matías Fidemraizer

Reputation: 64933

It's a convention based on HTTP standard. REST is built on top of convention over configuration paradigm. That is, a set of conventions avoid a lot of boilerplate and configuration.

For example, HTTP 1.1 standard says:

  • GET: The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process

  • POST: The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line [...].

...and so on.

Upvotes: 5

Related Questions