What is REST actually?

 REST is about creating representation(like JSON or XML or any other format.) of object's current state(like data in database) and transferring that representation over network. Rest is the set of constraint/convention.

Resources are decoupled from their representation so that their content can be accessed in a variety of formats, such as HTML, XML, plain text, PDF, JPEG, JSON, and others. Metadata about the resource is available and used, for example, to control caching, detect transmission errors, negotiate the appropriate representation format, and perform authentication or access control

At ground level , Rest is nothing more but a collection of principles


  1.  Communication should be stateless : Server should not store any state . If required it should be part of message
  2.  State should be representational : Internally resource at server can be in one form but it should be able
  3. to change it representation. An object referenced by one URI can have different formats available. Different platforms need different formats. Mobile may need JSON whereas desktop may need XML
  4. . HTTP verbs like GET, POST, PUT, and DELETE must be followed religiously.
  5. . Resources should be addressable : Every resource on your network should have an specific address(specific URI)

REST vs HTTP (From )

The most significant constraints of REST that distinguish a RESTful application from just any HTTP application are : 

  1. Self-description : This constraint requires a RESTful request to be completely self descriptive in the users intent. This allows clients/proxies/caches to act on the message safely.
  2. HATEOAS(Hypermedia as the Engine of Application State ) : This constraint is about turning your application into a web of links where the client's current state is based on its place in that web. It is a tricky concept and requires more time to explain than I have right now.

Comments

  1. AnonymousJune 27, 2020 at 10:48 AM

    This is my doubt could you please help

    https://stackoverflow.com/questions/62612122/in-representational-state-transfer-what-does-state-transfer-exactly-mean

    ReplyDelete

Post a Comment

Popular posts from this blog

How to solve javax.net.ssl.SSLHandshakeException ?

This blog is about how two secured web application on SSL can communicate with each other without get certificate error i.e. SSLHandshakeException Error developer generally face When web_application_A with self signed certificate  tries to connect to web_application_B (with same self signed certificate), sometimes you must have got below error detailed message sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target cause javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Details oF mine environment :-  I got same error . Here are the environment details Webserver :- Tomcat -6 OS :- Windows 7 Java Version :- 1.6 web_application_A :- Port 8443 web_applicat...
Read more

When to use Java 8 Optional instead of traditional null pointer check ?

My project has recently moved to Java 8. Now, I see applications flooded with Optional objects mainly to check the Null Pointer on an object. Before Java 8  code style to check the null pointer Employee employee = employeeServive.getEmployee(); if(employee!=null){     System.out.println(employee.getId()); } After java 8  code style to check the null pointer Optional<Employee> employeeOptional = Optional.ofNullable(employeeService. getEmployee()); // Another way of implementing above  where service itself will return Optional<Employee> employeeOptional = employeeService.getEmployee(); if(employeeOptional.isPresent()){     Employee employee = employeeOptional.get();     System.out.println(employee.getId()); } Which one is better to check Null Pointer I see  style 1 is better when intention is just to check Null Pointer. So I find, style 1 is more clear and lesser lines of code. In this case I see devs are...
Read more