If you have a limited budget and you want to use Oracle SOA Suite, and your company does not have an agreement with Oracle forget it.
Budget aside, Oracle SOA suite price fit enterprise and large departmental projects. Some knowledge on Oracle DB and Weblogic is especially required if you deploy your application in production. At the development time, a VM or a container is convenient to start developing, but at the Runtime on production, advanced knowledge is mandatory. So, if you need to connect a file system to a database, Oracle is over-powered for your case, and a simple Camel application is enough to do it.
Suppose you plan to create workflows of services AàBàCàD (vs implementing service orchestrations) you can use Oracle SOA Suite, especially if you already have an Oracle License that covers the cost of the tools. Nevertheless, I think that Oracle SOA Suite designer focused on service-orchestration more than workflows and consequently tools such as WSO2, Dell Boomi or Mule would be more efficient.
Oracle’s tool is performant when complex business processes must be implemented, and sophisticated service composition is required. Reliable and efficient, the SOA suite allows you to develop robust service-based integration platforms. In this area, Oracle competes with Tibco, WebMethods, Biztalk and OpenESB.
So, regarding the technologies used in your company, you could prefer Biztalk, Tibco, WebMethods or OpenESB to Oracle. As explained in one previous review, Oracle and OpenESB have been designed by the same team (Sun->Oracle), and there are fewer differences between both products than with the others. If your company is not linked to a technology (ex: Biztalk, C#, Windows) and the price is a decisive criterion, try to add Oracle SOA suite in your Oracle licenses, or link Webmethods within your agreement with Software AG, it will be cheaper for your budget. Else, you can try OpenESB, which is less expensive than the products in this category.
Do not hesitate to use Oracle SOA suite if you are an Oracle customer who wants to implement complex business processes in a service-based architecture project. Else consider the type of application (Workflow vs Orchestration) and the price of the product, the learning curve and the skill available in your production team.
I would recommend others to use Oracle SOA Suite, it's a great product. Now that we have the cloud solution, if your other products are in the cloud, then you can implement the cloud-based version. Most of my applications are on-premise, and that is why I am using the on-premise version. I would recommend the solution to anyone who wants stable, scalable, very versatile, and resilient, integration software. I rate Oracle SOA Suite an eight out of ten.
This is a good product and I can recommend it to others. That said, there are a lot of new products that are coming onto the market, including open-source solutions. If people are starting from scratch then I would recommend evaluating several of them. I would rate this solution an eight out of ten.
For integrating with Oracle solutions, such as Oracle EBS, which has an integrated SOA Gateway which can connect to an instance of Oracle SOA Suite to automate various processes, this is the best solution. As it is built on proven robust enterprise grade BEA technology, like WebLogic server, it is perfect for large deployments.
Collect your requirements and be clear with what you need. Before starting a concrete project or even before doing the final sizing, talk with others who have already implemented the solution or have reliable experience in this area. This will help you to get things right from the beginning and help you to avoid running into pitfalls. Do not undersize the environment and always keep in mind what will come in the future. The product can be used to build a company's robust foundation regarding a enterprise-wide integration platform without hesitation, which we already did in different project contexts. Because the platform helps to solve complex problems, it is complex itself and so not that easy to understand and to learn. The learning curve is high accordingly. EDIT: To ensure robustness and easy changeability of the developed services and components, my recommendation is to set up a Continuous Integration (CI) environment as a first step in every project. The CI environment is the central platform for automated test executions as well as for deployment automation and is - from my point of view - absolutely needed to succeed with complex integration implementations.