What does webservice 'consuming' and 'providing' mean?

CONSUMING or PROVIDING?

In web service terminology, the opposite of "consuming" a service is often referred to as "providing" or "offering" a service. When a client consumes a web service, it means that the client is making requests to the service to utilize its functionality. Conversely, when a service is provided, it means that the service is being provided (ie: made available) for clients to consume.

Consuming a web service involves a client application sending a request to a web service, which then processes the request and sends back a response. This interaction allows different applications to communicate and share data over a network, typically the internet.

For example, if you have a weather app on your phone, PC or even IBM system, it might consume a web service to get the latest weather data. The app sends a request to the weather service's server, which processes the request and returns the current weather information to the app.

Providing a web service involves the host application webservice responding to a request and sending back a response. 

Simple right?

What are the common protocols for consuming web services?

There are several common protocols used for consuming web services, each with its own strengths and use cases:

  • HTTP/HTTPS: These are the most widely used protocols for web services, providing a foundation for data exchange over the web. HTTPS adds a layer of security by encrypting the data.
  • SOAP (Simple Object Access Protocol): A protocol that uses XML to encode its messages. It is known for its robustness and extensibility, often used in enterprise environments.
  • REST (Representational State Transfer): An architectural style that uses standard HTTP methods (GET, POST, PUT, DELETE). It is lightweight and easy to use, making it popular for web APIs.
  • XML-RPC (XML Remote Procedure Call): A protocol that uses XML to encode its calls and HTTP as a transport mechanism. It is simpler than SOAP but less flexible.
  • JSON-RPC: Similar to XML-RPC but uses JSON instead of XML, making it more lightweight and easier to parse.
  • gRPC (gRPC Remote Procedure Call): A high-performance, open-source framework that uses HTTP/2 for transport, Protocol Buffers as the interface description language, and provides features such as authentication, load balancing, and more.

These protocols enable different applications to communicate and share data effectively, regardless of the underlying platforms or languages.

Done?
 Mark lesson complete
Previous Lesson
Next Lesson
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>