fuse-service-registry | Red Hat Fuse

fuse-service-registry is a Java library. fuse-service-registry has no bugs, it has no vulnerabilities and it has low support. However fuse-service-registry build file is not available. You can download it from GitLab.

The recommended way to build web services is to follow an API-First approach. It ensures a contract between the client and the server is defined, and with which both parties need to be compliant. In this tutorial, we've used APICurio to create an OpenAPI interface. It's UI is very intuitive and you can easily switch from the point & click interface to the source view where you can edit directly if you desire full control. We've also created a WSDL definition to expose a SOAP backend service which we'll integrate with. Normally, the interfaces (REST/SOAP) are included in the source code as part of the projects. They are used to create the JAVA structures that Fuse needs to generate/validate the data that goes in and out. From an implementation point of view this causes no problem and still follows the API-First approach. However, they are not easily reachable to external teams. It is preferable to have a central Service Registry acting as the 'Source of Truth' that keeps all interface definitions. The focus of this small tutorial is to serve as a guide on how to configure a Fuse project to obtain its interfaces from Red Hat's Service Registry. Fuse would then fetch the interfaces from the Service Registry when compiling and packaging the project to produce the deployable unit.