Differences between SOAP(Simple Object Access Protocol) and REST( Representational State Transfer).

The differences between SOAP and REST are:-

 RESTful web services and SOAP both have their own set of advantages and disadvantages. A REST web service, for example, is often a superior choice when time is of the essence, while SOAP triumphs in designing the services with various,non-CRUD methods. Unless otherwise specified by the Web Services provider, the type of web service implemented by a partner is determined by the company's requirements. Amazon and eBay both employ web services for REST and SOAP. And, as more firms become service focused and experiment with new features, they will be forced to accommodate both types.


SOAP

  • It stands for Simple Object Access Protocol.
  • It is an XML-based messaging protocol.
  • It needs more bandwidth and resources for better web performance.
  • SOAP enforces XML as a message format.
  • It has not great performance as compared to REST.
  • SOAP defines its security.
  • It does not support error handling. 
  • SOAP is a heavyweight XML protocol that requires more coding to send a message.
  • It cannot be cached.
  • SOAP messages are wrapped in an envelope and sent to any transport mechanism such as SMTP, FTP, HTTP, or any protocol.


REST 

  • It stands for Representational State Transfer.
  • It is not a protocol. It is an architectural style for distributed hypermedia systems. REST requires less bandwidth and resources as compared to SOAP. 
  • It is not specifically applied that the message format must be XML or JSON, etc. 
  • It has better performance as compared to SOAP, is less CPU intensive, has lesser code, etc. 
  • REST inherits security measures from the underlying transport. 
  • It has built-in error handling.
  • It is lightweight, scalable, and maintainable.
  • It can be cached.
  • It relies on the HTTP protocol for communication between two machines.





Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)

Discuss classification or taxonomy of virtualization at different levels.