... is a pattern with two modules, a connector module that can be used to encapsulate an external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

Same as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

... tries to fetch data from local cache entity, if not there, get single entry from the external system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

... caches only summary data that is frequently lister, joined or searched. Full detail for a ) single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

Same as ECS with local replica but synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.

Above is the answer

framework to support Architecture Conventions for Modules in Outsystems

framework to support application architecture design in Outsystems

framework to support Architecture Design Process in Outsystems

M_CS

_CS

mobile_CS

m_cs

m_CS

... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

Same as ECS with direct integration, but through an Enterprise Service Bus

... is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

... tries to fetch data from local cache entity, if not there, get single entry from the external p system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

Same as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

Same as ECS with local replica but synchronization logic is separated. Pro: Code

independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

... caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

... is a pattern with two modules, a connector module that can be used to encapsulate an external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

... tries to fetch data from local cache entity, if not there, get single entry from the external system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

Same as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

Same as ECS with local replica but synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

Limit Server side calls to online transactions or Synchronization. Do the bulk of the operations on the Client Side before passing information to the Server Side.

Synchronize on every screen or online event for better granularity

No direct calls to backend systems. Do call to Outsystems Core Services and Outsystems will handle the interaction with external backend systems.

Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.

Generic Library module.

Reusable UI Patterns for layout and display only - no Business logic.

Theme, look & feel elements, menu, etc.

technical wrapper to consume and normalize an external service.

to have several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

Concepts are disclosed to the Architecture team

Concepts are assembled into Modules

Concepts are added to the layers of the Architecture Canvas

Generic Library module.

several integration services with different systems, performing the same type of operation

(e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

Reusable UI Patterns for layout and display only - no Business logic.

Theme, look & feel elements, menu, etc.

technical wrapper to consume and normalize an external service.