Skip to main content

POST vs PUT

There are multiple ways developers will explain the difference between POST and PUT but fundamentally idempotency is the most distinguishing and important difference.

Idempotent HTTP requests will result in the same state on the server no matter how many times that same request is executed. GET, HEAD, PUT, and DELETE all have this attribute but POST does not.

So the operations that should be idempotent should not be handled by POST but by PUT.

For example,

'POST /tweets' will create a new tweet and might return a url to identify the new tweet resource with 'tweet/1007'

'PUT /tweet/1007' will either create a new tweet if it does not already exist, or replace the existing tweet with new information.


Remember, POST will always have a side-effect!

Comments

  1. Lucky Club Casino Site Review
    The Lucky Club luckyclub Casino is the best place to play online gambling. It offers a range of gaming options including blackjack, roulette,  Rating: 4 · ‎Review by LuckyClub.live

    ReplyDelete
  2. While you can to|you possibly can}'t be sure to|make sure to|remember to} win at these slots every time you play and you may't tell when these slot machines are able to hit, these are 코인카지노 those with one of the best slot machine odds. Finding what are one of the best type of slot machines to play and how to to|tips on how to} enhance your chances to win at slots is the dream of everyone into online playing. Lock in a win taking part in} Lock It Up – Dragon Fire™ and Legend of Nian™.

    ReplyDelete

Post a Comment

Popular posts from this blog

Best Practices: Config changes in Spring Boot

Any additional Spring configuration beyond what Spring boot auto-configuration provides, its always better to write separate @Configuration-configured classes. These @Configuration annotated classes will be picked up by component scanning and included in the Spring configuration. Its always judicial to avoid adding configuration to the primary Spring configuration class or application's bootstrap class.

@interface vs interface in Java

@interface is an annotation type declaration which resembles a Java Interface declaration - interface. Examples of standard Java annotations include @Override, @SuppressWarning etc. Java has always had meta-data tags like transient and Javadoc tag @deprecated. Annotations do not impact the flow of the program but impact the way a program is treated by tools or libraries.