<![CDATA[Codestreet]]>https://codestreet.iohttps://codestreet.io/img/substack.pngCodestreethttps://codestreet.ioSubstackFri, 24 Apr 2026 22:42:26 GMT<![CDATA[Understanding HTTP Verbs: A Guide to Web Communication]]>https://codestreet.io/p/understanding-http-verbs-a-guidehttps://codestreet.io/p/understanding-http-verbs-a-guideSun, 03 Dec 2023 18:34:37 GMT

HTTP (Hypertext Transfer Protocol) is the foundation of data communication on the World Wide Web. It defines how messages are formatted and transmitted, and more importantly, how web servers and browsers should respond to various commands. HTTP verbs, also known as HTTP methods, play a crucial role in this communication by specifying the type of action the client wants to perform on a given resource. In this article, we'll explore the commonly used HTTP verbs and their significance in web development.

  1. GET: Retrieving Data

    The GET method is used to request data from a specified resource. It is a safe and idempotent operation, meaning it should not change the state of the server, and making multiple identical requests should have the same effect as making a single request. GET is commonly used for fetching web pages, images, and other static content.

  2. POST: Submitting Data
    POST is employed when the client wants to submit data to be processed to a specified resource. It is not idempotent, and the act of submitting the same data multiple times may result in different outcomes. POST is often used for form submissions, file uploads, and other actions that may alter the state of the server.

  3. PUT: Updating Resources

    PUT is utilized to update a resource on the server or create it if it doesn't exist. It is idempotent, meaning repeated identical requests have the same effect as a single request. Developers commonly use PUT to update data entities on the server, such as updating a user's profile information.

  4. DELETE: Removing Resources

    DELETE is employed to request the removal of a resource identified by a specific URL. Like PUT, it is idempotent, and multiple identical requests should have the same result as a single request. DELETE is often used for deleting records, files, or other resources on the server.

  5. PATCH: Partial Updates

    PATCH is used to apply partial modifications to a resource. It is typically employed when updating a resource where the client only wants to apply changes to specific fields, rather than submitting the entire updated resource. This can be beneficial for reducing bandwidth usage and improving efficiency.

  6. HEAD: Retrieving Headers

    The HEAD method is similar to GET, but it requests the headers of the resource rather than the actual data. It is useful when the client needs to check the last modification date or other metadata without downloading the entire resource.

  7. OPTIONS: Retrieving Server Capabilities

    OPTIONS is used to describe the communication options for the target resource. It allows the client to determine the communication options available on the server, such as supported methods or server capabilities.

Understanding HTTP verbs is fundamental for web developers, as they dictate how clients and servers interact. Each HTTP verb serves a specific purpose, and choosing the right one is crucial for efficient and secure web communication. By grasping the nuances of GET, POST, PUT, DELETE, PATCH, HEAD, and OPTIONS, developers can build robust and effective web applications that adhere to the principles of RESTful architecture.

Thanks for reading Codestreet! Subscribe for free to receive new posts and support my work.

]]><![CDATA[REST/RPC/GraphQL]]>https://codestreet.io/p/restrpcgraphqlhttps://codestreet.io/p/restrpcgraphqlMon, 05 Sep 2022 04:48:49 GMTREST

Pros

  1. Good for exposing CRUD operations.

  2. Easiest to maintain compared to others.

  3. Standard method names, arguments and status codes.

  4. Utilizes HTTP features.

Cons

  1. Payload is big 

    1. JSON which is human readable.

    2. Getting the entire User entity while I need the user's first and last name only.

  2. Multiple HTTP roundtrips.

    1. If you want to get a resource and its sub resource, you need to make a call for the resource and then another call for the sub resource. There is no way to combine the two calls into one in a RESTful way.

RPC

Notes

  1. It’s all about actions

  2. Example slack.

  3. Usually supports GET for read only requests and POST for everything else.

  4. Very popular among API providers recently.

  5. gRPC.

Pros

  1. Good for exposing several actions.

  2. Small Payload

    1.  Because it’s in binary.

    2. Payload is associated with the action itself, so only the required data is transmitted.

  3. High performance because they are action oriented.

  4. Easy to understand as the action is usually the part of the request.

  5. Github.

Cons

  1. Difficult to discover.

  2. Limited standardization. Referencing documentation is important.

  3. Function explosion.

GraphQL

Notes

  1. Developed by Facebook.

  2. Expose a single endpoint as an entry point.

  3. Client then specifies what they need.

Pros

  1. Good when the client needs filtering/flexibility.

  2. Small payload because the response contains only the data client needs.

  3. Clients can request multiple nested levels of data.

  4. Don’t need versioning. 

Cons

  1. Complexity on the server.

  2. Optimizing performance can be difficult.

    1. Working with external users, it becomes difficult to identify different use cases.

  3. Too complicated for simple APIs.

]]>