Introduction

We will introduce the concept of a distributed project container. This is a way to include a (remote) application into your application.

Reasons to do this are:

• being able to split up applications
• being able to scale individual applications
• being able to model more intuitively

.... external flow [editor] ....

... Concept: External Flow Container [Editor] ...

Goal

The goal of this mechanism is to be:

• No monolyth
• agile applications
• maintainable

Architecture

x

Elements

To be able to use this functionality a new container type is to be used: the AQ_ExternalFlow. 

Also the concept of a contract is needed: see Contract module.

Prerequisites

xxx

• Build it with current studio concepts

Pros

xxx

• To split up large applications
• In control
• Short release cycle
• Release part is small
• Target inactive ...
• Docker ??

Pitfalls

xxx

• This construction should not be used as a "doel an sich"
• There is a chance of circular reasoning
• Sessions can break
• Datamapping ...

Installation

x