Have you ever thought about integrating applications
Have you ever thought about integrating applications

using simple and uniform
using simple and uniform

web service interfaces ?
web service interfaces ?

Rest or Representational State Transfer is an
Rest or Representational State Transfer is an

architectural style that defines a way
architectural style that defines a way

to make uniform API calls through
to make uniform API calls through

RESTful web service interfaces.
RESTful web service interfaces.

This allows for easy access of APIs
This allows for easy access of APIs

implemented at the server end, via the HTTP protocol.
implemented at the server end, via the HTTP protocol.

Client server applications
Client server applications

developed in any language such as Java
developed in any language such as Java

can support REST to implement the
can support REST to implement the

uniform web service interfaces.
uniform web service interfaces.

But, do the uniform web service interfaces work well in REST?
But, do the uniform web service interfaces work well in REST?

Consider a traditional API library
Consider a traditional API library

associated with customer and orders data.
associated with customer and orders data.

Let's say you have four APIs
Let's say you have four APIs

one to add new customer details,
one to add new customer details,

one to retrieve the existing customer details
one to retrieve the existing customer details

one to remove the existing customer details, and another
one to remove the existing customer details, and another

to modify the existing customer details.
to modify the existing customer details.

These four APIs have to be exposed by your application.
These four APIs have to be exposed by your application.

This makes your APIs difficult to use
This makes your APIs difficult to use

and less compatible with external client applications.
and less compatible with external client applications.

With REST, the interfaces
With REST, the interfaces

are designed so that the external user
are designed so that the external user

or client application can easily call
or client application can easily call

the RESTful uniform web service
the RESTful uniform web service

interface with less compatibility issues.
interface with less compatibility issues.

For example, you could use a web application
For example, you could use a web application

to web enabled those same
to web enabled those same

four APIs, to the external world by
four APIs, to the external world by

defining '/Customers', as the RESTful web service interface.
defining '/Customers', as the RESTful web service interface.

Any of the C R U D
Any of the C R U D

operations would be invoked at the
operations would be invoked at the

client application URL in association
client application URL in association

with the respective HTTP verbs, over the
with the respective HTTP verbs, over the

'/Customers' uniform web service interface.
'/Customers' uniform web service interface.

With REST, representations of the resources that are transferred between
With REST, representations of the resources that are transferred between

client and server can use XML or YAML,
client and server can use XML or YAML,

but most commonly use JavaScript object notation
but most commonly use JavaScript object notation

or JSON format.
or JSON format.

JSON is a simple lightweight data representation
JSON is a simple lightweight data representation

format, with less metadata.
format, with less metadata.

This can be used to exchange data
This can be used to exchange data

between software applications.
between software applications.

Here the structure of the JSON snippet
Here the structure of the JSON snippet

specifies the HTTP methods, HTTP protocol
specifies the HTTP methods, HTTP protocol

host server, and resource URL followed
host server, and resource URL followed

by payload with data values, data objects or both.
by payload with data values, data objects or both.

And here for JSON payload the details are encapsulated in
And here for JSON payload the details are encapsulated in

the JSON body tags. This JSON payload
the JSON body tags. This JSON payload

can be designed to be processed
can be designed to be processed

accordingly with the respective REST API call,
accordingly with the respective REST API call,

and sent to the host server, in
and sent to the host server, in

combination with any of the HTTP verbs.
combination with any of the HTTP verbs.

The different HTTP response codes are
The different HTTP response codes are

based on the type of HTTP request used.
based on the type of HTTP request used.

To create a new customer,
To create a new customer,

let's make a POST request and send to the
let's make a POST request and send to the

web application instance via the other RESTful
web application instance via the other RESTful

web service '/Customers', with the
web service '/Customers', with the

specific annotations, along with the JSON payload.
specific annotations, along with the JSON payload.

The JSON payload contains new
The JSON payload contains new

customer details. The RESTful web service
customer details. The RESTful web service

application returns the status code 201,
application returns the status code 201,

to confirm new customer created.
to confirm new customer created.

To retrieve existing customers,
To retrieve existing customers,

let's make a GET request and send to the
let's make a GET request and send to the

web application instance, via the other RESTful
web application instance, via the other RESTful

web service '/Customers', with the
web service '/Customers', with the

specific annotations. The output has the
specific annotations. The output has the

requested customer details in JSON format.
requested customer details in JSON format.

The RESTful web service application
The RESTful web service application

returns the HTTP status code 200,
returns the HTTP status code 200,

to confirm the requested customer
to confirm the requested customer

details are retrieved in JSON format.
details are retrieved in JSON format.

To delete any existing customer details,
To delete any existing customer details,

let's make a delete request and send to the
let's make a delete request and send to the

web application instance, via the the RESTful
web application instance, via the the RESTful

web service '/Customers', with the
web service '/Customers', with the

specific annotations. The RESTful web
specific annotations. The RESTful web

service application returns the
service application returns the

status code 204, to confirm the requested
status code 204, to confirm the requested

customer details are deleted in the back end,
customer details are deleted in the back end,

hence nothing showing in the output console.
hence nothing showing in the output console.

REST is an architectural style
REST is an architectural style

that defines a way to make uniform API calls
that defines a way to make uniform API calls

through RESTful web service
through RESTful web service

interfaces via the HTTP protocol along with
interfaces via the HTTP protocol along with

the suitable HTTP verbs.
the suitable HTTP verbs.

To learn about cloud standards such as SCIM,
To learn about cloud standards such as SCIM,

OAuth and OpenID Connect
OAuth and OpenID Connect

check out the other videos in this series.
check out the other videos in this series.

Thank you for watching.
Thank you for watching.