Oracle Data Service Integrator vs. WSO2 Enterprise Integrator

Once Oracle Data Service Integrator is set up properly, it is quite simple to snatch data from a myriad of disparate sources and put them into a single repository. Due to cost factors, it is not for the faint of heart; however, if you can handle it, the benefits will quickly outpace the initial investment. To take full advantage of the power of ODSI, I would recommend the training that Oracle provides.

Incentivized

The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.

• Very easy to use. Very easy to just grab data when needed.
• Very robust and has so many features to move and transform data.
• Functionality is very easy to implement with other Oracle data products.

Incentivized

• Service chain pattern
• Message transformation
• Call more than one backend service
• Call service with different protocoll as the client use
• Use file as input
• Use mail as input

• If not bundled with other products, the price can be prohibitively expensive
• SAP connectors tend to be a little expensive and slightly difficult to use
• The audit module had some difficulties debugging failed instances

Incentivized

• View deploy artifact in date time order
• Easy way to map data
• Easy way to manage payload

While we tested and evaluated multiple data service providers, we came to choose Oracle Data Service Integrator since our infrastructure was so heavily dependent on Oracle software. The implementation would be easier and the difference in the number of features and performance wasn't enough to sway us in another direction.

Incentivized

We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.

• It provided terrific bulk data movement and data transformation services which we desperately needed
• It allowed to reduce development costs and lower the total cost of ownership among disparate architectures
• The enterprise edition's ELT allowed us to generate native code for wildly varied RDBMS

Incentivized

• Reduce development time to the service integration
• We can use junior developer
• Clustered in easy way