Amazon Web Services vs Oracle Data Integrator

• The development and administration tools work well, including a consistent API and adequate management console. In terms of business process, it provided an effective "escape valve" for new product development that would have been much more onerous to deploy if we had to provision physical hardware and arrange for associated IT resources.

Read full review

• Is simple and easy to learn, thanks to the low number of development objects that it has (mainly: interfaces, procedures and packages, plus variables).
• It allows you to integrate data from and to any kind of technology. This is a strong point since it's able to connect practically to any technology, Oracle and not.
• It allows you to create integration flows that manage through steps on any task.
• It provides both an automatic and a customizable management of integration mistakes.
• If you feel stronger in developing through hard code, ODI allows you to integrate anything through procedures.
• It supports almost any kind of developing language, like SQL, PLSQL, Java, Javascript, C#, and so on.
• It's easy to backup, since it provides a native way to export all the developments but also its relational repositories (master and work) can be exported from the database where they reside.

Read full review

• AWS has a record of occasional severe outages, which has a cascading effect on the large number of high-profile services that now run on its infrastructure. Despite the spectacular nature of these outages, it is unlikely that a self-managed data center would achieve significantly better uptime.
• It is also the case that AWS outages can be mitigated with effective use of multiple deployment 'zones' and regions. This is something that any mission-critical application should be doing anyway as part of disaster recovery preparations.

Read full review

• The Java framework does not stand up to the mark. It crashes frequently. There is a long [list] of improvements required in terms of client tools framework.
• Though Oracle Data Integrator lets people login from a web browser to monitor different activities, it crashes and performs very poorly when logged in out of network. Even Oracle Data Integrator client tools don't perform well on a remote desktop. Increasing Java buffer is one of the workarounds, that might work. So, a better client tools and interface is a big advantage.
• Navigation is another pain area. It is very difficult to find out the precise error, in case of a failure, in Oracle Data Integrator. In Informatica, it is a cake walk to pull out a session log that shows up the exact reason for failure. Although Oracle Data Integrator is tightly integrated to database, it is very poor in providing the exact error at high level. One has to dig through to get it.

Read full review

• Positive: Faster provisioning of infrastructure.
• Positive: Lower upfront costs.
• Negative: Integration of AWS to enterprise apps.

Read full review

• It quickened our development of interfaces.
• Allow us to replace some interfaces based on TXT files with direct connection, and thus turning our environment more safe and SOX compliant.

Read full review