Web Service Broker Design Pattern
Start course
3h 59m

In this course, we will learn the concepts of microservice and spring framework with a focus on design patterns.

Learning Objectives

  • Learn about various design patterns

Intended Audience

  • Beginner Java developers
  • Java developers interested in learning how to Build and Deploy RESTful Web Services
  • Java Developers who want to develop web applications using the Spring framework
  • Java Developers who want to develop web applications with microservices
  • Java Developers who wish to develop Spring Boot Microservices with Spring Cloud


  • Basic Java knowledge

Hello, dear friends. In this video, we will examine the Web Service Broker Pattern. So, let's begin. The Web Service Broker uses web protocols and XML. We can use this pattern to expose and broker the services. Imagine a circumstance where multiple organizations are lined up in order to request info from a number of service providers. A broker provides the central medium, which makes the transfer of information happen. It is a general gateway or an address in order for the client apps to be able to access a large, diverse variety of services. These services might need a broker in order to make an interaction with either only a single server app or multiple server apps. The broker perform certain tasks.

It's responsible for receiving SOAP requests from the client apps in XML format along with authenticating the request and checking for the authorization. You can also use it to generate calls to multiple server apps, which depends on the nature of the request. As you can see in this UML, this pattern also has some participants. The Client can be anything that is capable of making a web service request. The EndpointProcessor is a servlet. It is the initial point of entry into the web service and is responsible for accepting and processing a request. The request is typically based on an HTTP request, such as a SOAP request. Typically, the endpoint process is built into the runtime system, such as when using JAX-RPC. You can also build a custom endpoint processor.

The Web Service Broker is a web service that serves as a broker to one or more services. Those services can be J2EE services, such as Session Facade and application services or legacy EIS systems. The Web Service Broker can be realized in three ways. The business service can be a J2EE Session Facade, an application service or a POJO Facade to EIS. In fact, you will not come across this pattern very often. So, there will be no questions about this pattern in any exam. And so, that's all you probably need to know. We'll continue with Business Tier Patterns. In the following video, we will look at the service locator pattern. See you in the next video my friends.


About the Author
Learning Paths

OAK Academy is made up of tech experts who have been in the sector for years and years and are deeply rooted in the tech world. They specialize in critical areas like cybersecurity, coding, IT, game development, app monetization, and mobile development.