OIC Antipatterns or Best Practices

Oracle anti-pattern recommendations in one post-

1     Integration which talked too much 

Avoid fine grain invokes inside loop. This impacts downstream applications and can alter cloud pricing. 

Instead use Application or Adapter capabilities to send batch requests for processing either as request or opaque attachments. 

2     Scheduled Job which never gave up

Avoid scheduled job to process all the files in one schedule. Long running job starves other jobs which results in getting killed by the framework.
Instead limit the files to be run. Secondly call the same integration after limit is reached remembering the last processed file.

3     Look, I hacked my Integration!

Avoid externally updating the IAR file while updating complex constructs in XSLT. Integration metadata might get corrupted leading to activation failures.
Instead just alter the XSLT using import XSLT option.

4     Synchronous flow which tried to do too much

Request triggers a complex processing involving enrichment and updates across multiple system. Susceptible to timeouts, marginal slow down, half done processes.

Use asynchronous services, coarse grain callouts, avoid multiple chatty calls.

5     Too Many keys for the same door!

Multiple developers duplicate same connections. This leads difficulty in managing connections when there is an endpoint update needed resulting in bad operational maintenance. There should be a reviewer validating the connections being unique.

6     Read more than what I could chew

Read a file with large number of records and process individual records. Reading large file in memory consumes resources for other running integrations.

Instead download file and read in segments.

7     I Skipped the Spring Cleaning ...

Integrations created during development continue remain activated without being decommissioned. Bad to manage and maintain.

Always deactivate or delete the unused integrations. Its always always present in the GIT or any other repository.