Oracle Service Bus Reviews

It's sort of a one-stop shop for web services. All of our web services interact with each other. Instead of calling specific server host names and specific URLs, we call the OSB service bus URL that's configured for that specific client. It's very simple to know where things are going because we can generate the URL specifically with our naming convention, so that we know where it goes, who's calling it, what environment it's for.

With the most recent version, 12c, I'm still getting use to using it, learning how to use it, how to configure it. The Oracle documentation is OK, but there aren’t a lot of good examples for me to follow. It describes the concepts and what it can do, but how to apply them has been a struggle, so far. I'm still looking for help in that area.

I have been using it for at least eight years.

It is very stable. It processes hundreds of thousands of transactions per month. Once, with our primary system for handling customers coming into our site for orders and order information, the customer would come in and send an email to our internal users; that crashed our Exchange server but OSB kept running. It was fine. It's very stable and it has to be for what it does. It's kind of like a load balancer in a way; if it goes down, then everything behind it will stop operating.

It can meet our scaling needs moving forward. I would be surprised to see it have a problem with scalability.

Technical support is OK. We know what to expect from Oracle support. You're going to ask a question. Generally, you're provided with a document: "Check out this support doc. Does this answer your question?" If it doesn't right away, then they'll take a closer look.

It's OK. It's not ideal, but after working with it for so many years, I know what to expect out of it.

Initial setup is pretty straightforward for an Oracle product. Again, we know what to expect with it and it works well.

When I select a vendor to work with, I look for reliability and ease of use. Performance is everything and this has proven itself over the years. That's why we keep using it.

I use this solution for development with complex integration.

This product is not complicated and very easy to learn.

Integrating this solution with other technologies is not difficult.

There are times when I select components in composite and they do not appear, and I cannot figure out why. This can happen when you develop a big project and clone it, then look for a service. Sometimes, you cannot find your work. It's a big problem.

This solution is stable, although sometimes we see some strange behavior in the developer, where some parts do not appear. In cases like this, we need to reset.

I have not contacted technical support.

Prior to this solution, we used Java and Java Brains suite. Using Java is more complicated, and these things are taken care of by Oracle Service Bus.

Overall, this product is quite good and I feel comfortable when I use it.

I would rate this solution a nine out of ten.

We use Service Bus to expose our service endpoints.

Service Bus is good at routing and transformation. 

The weak point of OSB is that it is not suitable for modern application implementation like microservices which need smart endpoints. With a dumb pipe through and rest API or lightweight message, Bus is not. 

I've used Service Bus for one or two years.

For a microservices solution, we preferred to use rest APIs and a lightweight message Bus such as Kafka or RabbitMQ for integration.

I rate Oracle Service Bus six out of 10. OSB isn't suitable for working with modern applications. We can use it for a monolithic application, not in microservices techniques. 

We use the solution for message processing. 

From a technical perspective, the interface is fine and the solution is quite robust.

There are several improvements that could be made to the product. Security needs to be more integrated, there are so many new security techniques on the market that could be integrated. They should also be embedding API key and other security mechanisms. I find the solution to be somewhat lightweight. 

The solution is scalable although sometimes there is a memory bottleneck and the solution crashes. 

I carried out the deployment and it took a maximum of two hours. We have five users and one specialist who deals with maintenance. 

To choose this solution would depend on company priorities. If someone is looking for a highly scalable solution with security features embedded there are many other options available. If the case scenario is a customer who is already using Oracle Stack and has a good relationship with Oracle then I would recommend OSB if they can survive with the built-in security model. I would definitely recommend it for some customers.

I rate this product seven out of 10. 

This solution can be used for internal connectivity between enterprise applications and a Telco client.

I like the ease of deployment and the ease of implementation.

The support for GraphQL needs to be improved, and the response time for global support could be faster.

We have been implementing this solution for more than eight years.

It's a stable product. There are no issues with stability.

It's a scalable solution.

We have three customers who are using this solution.

Local support is very fast, but if you have to escalate the ticket to the global team it takes a lot of time. It could be time-consuming.

Global support response time could be faster.

The initial setup is straightforward.

It took me an hour and a half to install.

We have a team of five including one manager, and four engineers to maintain this solution. 

I completed the installation myself.

I would recommend this solution for large enterprises.

I would rate Oracle Service Bus a nine out of ten.