Oracle Integration Cloud: Building Integrations That Survive Production · Module 3 · Connections and adapters
The database adapter
Lesson 27 of 175 · 2 min
Polling and calling a database directly. Powerful, occasionally correct, and the fastest way to create a dependency nobody documented. WHERE IT IS LEGITIMATE: a database that is genuinely the system of record with no application layer in front of it — a legacy system whose only interface is its schema, a reporting store, a staging area somebody built for exactly this. In those cases the database IS the API, and using it is not a workaround. WHERE IT IS NOT: reaching into an application's database to avoid its API. That is unsupported by the application, it bypasses every validation and business rule the application enforces, and it breaks at the vendor's next upgrade. For Fusion it is not available at all, which is a boundary the Technical course explains, and it is worth noticing that the constraint people resent there prevents exactly this class of problem. THE CONNECTION THAT QUIETLY…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.
In this module: Module 3 · Connections and adapters
- 1What a connection is
- 2Choosing an adapterFree preview
- 3The REST adapter
- 4The SOAP adapter
- 5The FTP adapter
- 6The database adapter
- 7Testing a connection properly
- 8One connection or several
- 9Connectivity agents, and when you need one
- 10What breaks: four connection failures
- 11Lab briefing · Three connections, three systems
