Hello Nuno

I am not sure if I fully understant your proposal but at first impression, it seems to me that it only adds a new layer of complexity. 

Regards

@Alberto it doesn't add extra complexity, the complexity is already there and you can manage and validate it by means of the Application Architecture Canvas

https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/Designing_the_Architecture_of_Your_OutSystems_Applications/Application_composition/Applying_the_Architecture_Canvas_to_applications

@Alberto, Currently, you can already define Domains in Discovery (they can even be auto created from LifeTime Teams).

In a domain (vertical or horizontal) you can have one or more LifeTime Applications.

Nuno's idea, is to also implement the concept Business Application, as described in the OutSystems success document I shared in my previous reply (the blue rectangles).

So the decomposition of a solution will then be 

• One or more domains
• Each domain with one or more business applications
• Each business application with one or more LifeTime applications.

The idea is only about implementing the concept, as it does already exist, only now the OutSystems tools do not support it.

You could "misuse" domains for this and create a domain for every business application. But you would lose the concept domain.

Thanks, Daniel.

Much more clear now. 

One of the other benefits would be that it would provide a way to de-clutter the service studio application list. It becomes very complex when you have 100+ applications.