Oracle Visual Builder: Applications That Outlive Their First Release · Module 9 · Fragments, components and reuse
Sharing across applications
Lesson 95 of 176 · 2 min
What can be shared, THE VERSIONING QUESTION THAT COMES WITH IT, and WHO OWNS THE SHARED THING. Sharing across applications is where reuse stops being a technical decision and becomes an organisational one — which is why this lesson is mostly about ownership. WHAT CAN BE SHARED IS FRAGMENTS, COMPONENTS AND SERVICE CONNECTIONS. A common header, a customer picker, the definition of the Fusion endpoint everybody calls. And the case for it is exactly Lesson 3's: four applications each defining the same connection will disagree about one of its settings within a year. THE VERSIONING QUESTION IS THE ONE THAT DECIDES WHETHER THIS HELPS OR HURTS: WHEN THE SHARED THING CHANGES, WHO GETS THE CHANGE? IF EVERYBODY GETS IT IMMEDIATELY, YOU HAVE ONE VERSION AND NO DRIFT — AND A CHANGE THAT REACHES THREE APPLICATIONS NOBODY TESTED. Lesson 7's second failure: a shared component changed under three applications, two of…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.