Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
16 views4 pages

REST API Lecture 25112024 104836am

Web services are software applications that facilitate communication between different systems over the internet using standardized protocols like HTTP. The evolution of web services transitioned from earlier methods such as RPC, CORBA, and DCOM to more standardized approaches like SOAP and REST, which address issues of interoperability and scalability. SOAP uses XML for messaging in complex systems, while REST offers a lightweight alternative using HTTP verbs and endpoints for efficient data exchange.

Uploaded by

alyanman895
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
16 views4 pages

REST API Lecture 25112024 104836am

Web services are software applications that facilitate communication between different systems over the internet using standardized protocols like HTTP. The evolution of web services transitioned from earlier methods such as RPC, CORBA, and DCOM to more standardized approaches like SOAP and REST, which address issues of interoperability and scalability. SOAP uses XML for messaging in complex systems, while REST offers a lightweight alternative using HTTP verbs and endpoints for efficient data exchange.

Uploaded by

alyanman895
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Web Service: A web service is a software application that allows different

systems to communicate over the internet using standardized protocols, like


HTTP. It enables sharing of data or functionality between applications, regardless
of the programming languages they use.

Evolution of Web Services:

Before REST and SOAP became dominant for building web services, other
approaches and technologies were used. These earlier methods lacked the
standardization and flexibility.

1. Remote Procedure Call (RPC)

 Description: Allowed programs to execute code on a remote system as if


it were a local procedure or function.
 How It Worked:
o Used a client-server model.
 Limitations:
o Tight coupling between client and server.
o Platform and language dependency in some cases.

2. CORBA (Common Object Request Broker Architecture)

 Description: A standard defined by the Object Management Group (OMG)


for enabling communication between applications written in different
languages and running on different platforms.
 How It Worked:
o Used an Object Request Broker (ORB) as a middleware layer.
o Relied on Interface Definition Language (IDL) for defining the
communication contract.
 Limitations:
o Complex setup.
o Performance overhead due to ORB.
o Poor scalability for web-based systems.

3. DCOM (Distributed Component Object Model)

 Description: A Microsoft technology for communication between software


components on networked computers.
 How It Worked:
o Extended COM (Component Object Model) for networked systems.
o Required Windows environments.
 Limitations:
o Platform dependency (Windows-only).
o Not suitable for cross-platform web services.

4. Early HTTP APIs

 Description: Custom APIs built directly over HTTP without adhering to


specific standards like REST or SOAP.
 Limitations:
o Lack of standardization made maintenance and scalability difficult.
Before REST:

Now server sends the data as a response in two formats. JSON or XML.

But here is one issue.

Eg. http request, http response, respons edata, request data. Using all
these methods for large number of data was very complex. So to avoid
this we use RestApi.
5. Evolution to REST and SOAP

The above methods had limitations in interoperability, scalability, and simplicity,


especially as the web grew. SOAP (introduced in 1999) brought standardized
XML messaging, making cross-platform and cross-language communication
easier. REST (formalized in 2000 by Roy Fielding) introduced a lightweight,
scalable, and flexible alternative, better suited for the growing needs of the web
and mobile applications.

SOAP: SOAP or Simple Object Access Protocol is a messaging protocol. Is


allows to exchange the structure information without any platform. Soap uses
the XML data fromat due to the complexity. It is mostly used for complex
systems with strict standards ensuring security and reliability.

“Rest API creates an object and there after sends the values of the
objects in response to the client request”.
Two things are must for using Rest API. First is http verbs, which are POST, GET,
PUT, DELETE. Second Is End point/Resource. Which is after api/ . Rest API says
that end point should be same.

You might also like