16. Design - ADF Architectural Patterns - Cylinder

The author's recommendation: the ADF Architecture TV channel is a training course to extend customers' knowledge in ADF, it is not a marketing or promotional exercise from Oracle Corporation. If you've arrived on this episode by Googling in, please make sure to look at all of the content on the TV channel rather than taking this episode as a standalone topic.

This episode: In a previous episode the Sum of the Parts pattern explores the idea of placing Bounded Task Flows into separate workspaces, re-consuming them in a master application workspace through ADF Library JARs. The definition of what went in each BTF Workspace was fairly undefined. In this episode of the ADF Architecture TV channel Chris Muir explores making each BTF Workspace a cylinder, a self contained logical unit of BTFs and model code, along with a discussion what pros and cons this approach introduces.

Like to know more? Check out:

Watch the previous episode:
- Design - ADF Architectural Patterns - Two for One Deal

Watch the next episode:
- Design - ADF Architecture Patterns - Pillar

Subscribe to the channel:

See the episode index:
- ADF Architecture Square

[ADFArchitectureTV]

Good question. And this will be answered in an upcoming episode very soon!

Meanwhile look to the following whitepaper and the mention of "automagical" application module nesting:

(Sorry, YouTube doesn't allow me to include a link so you need to:

a) Google: Task Flow Transaction Fundamentals
b) In the relating PDF and search for "automagical".

[misgeburtt]

Regarding granularity - if we choose to be too thin, we will end up with a lot of AppModules - 1 per each cylinder.
I've read people hitting bad performance due to too much AppModules working against 1 database. If this is the common case, then defining maximum number of AppModules could help us defining the granularity.
What do you think would be the maximum number of AppModules for the whole application?

Thanks in advance for the answer!