We’re architecting a partner portal integration with Oracle CX Cloud 23C and debating between cloud-native API integration versus maintaining our existing on-premise connector infrastructure. I’d like to hear from others who’ve made this decision.
Cloud-native approach would use Oracle Integration Cloud (OIC) with REST APIs directly to CX Cloud services. On-premise approach keeps our current middleware servers with custom connectors. The cloud-native path seems cleaner but we’re concerned about losing fine-grained control we have with on-premise.
Key considerations for us: security implications of cloud-to-cloud integration, scalability during peak partner activity periods, and the long-term maintenance burden. Our partner portal handles about 500 concurrent users during busy periods with complex data synchronization needs.
What are others doing for partner portal integrations in cloud deployments? Any lessons learned from choosing one approach over the other?
We went cloud-native last year and haven’t looked back. OIC with REST APIs gives you built-in scalability that’s hard to match with on-premise infrastructure. During peak loads, OIC auto-scales the integration instances. With on-premise, we were constantly tuning middleware servers and hit capacity limits. The security model is actually better in cloud-to-cloud - OAuth 2.0 with short-lived tokens versus our old approach of long-lived API keys stored in config files.
I’d caution against rushing to cloud-native. We maintain on-premise connectors specifically for the control and customization. Our partner portal has complex business logic in the integration layer - data transformations, custom validation, multi-system orchestration. Moving that to OIC meant rewriting everything in their visual designer or writing custom code in Node.js. The on-premise connector maintenance isn’t trivial, but we have full control over performance tuning, custom caching, and can handle edge cases that would be difficult in OIC’s constrained environment.
Scalability is where cloud-native really shines. Our on-premise middleware could handle maybe 200 concurrent integrations before response times degraded. With OIC, we’ve tested up to 2000 concurrent partner portal sessions with consistent sub-second response times. OIC automatically provisions additional integration instances based on load. That said, you need to design your APIs carefully - chatty integrations with many round trips will still perform poorly regardless of infrastructure. Use bulk APIs and optimize payload sizes.
The maintenance burden comparison is interesting. On-premise requires patching servers, managing certificates, monitoring infrastructure, handling failover. With cloud-native, Oracle handles the infrastructure. However, you’re trading infrastructure maintenance for integration maintenance - OIC updates sometimes break integrations, requiring testing and updates. We spend less time on infrastructure but more time on regression testing after Oracle’s quarterly updates.