OutSystems Architecture-Specialist-11 - Architecture Specialist (OutSystems 11) Exam

... a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS

... 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)

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 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.

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

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 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

Core Modules and Foundation Modules.

End-User and Foundation Modules.

End-user and Core Modules.

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.