A. Promotes segregation and loose coupling of services

B. Optimizes lifecycle independence

C. Promotes abstraction of reusable services

D. Minimizes impact of changes

A. Reduces Costs : Architecture benefits are not only technical, but affect how you operate

B. Reduces Risk : Architecture is a cost effective way to mitigate substantial risks and ensure ^ success

C. Manages Complexity : Helps reduce emerging complexity by focusing on relevant properties and omitting irrelevant details, thus leading to simpler representation

D. Facilitate Change : When something comes up that requires you to veer from the origina design or path, architecture of your system can show you exactly what needs to change and help with communication and planning.

E. Supports Planning : Helps the team anticipate and build solutions

F. Helps Communication : Helps you to get buy in from the business and to communicate overall plan to them

G. Drives Consensus : Helps create common ground with the team

A. Is the end result of Architecture Design Proces

B. At this point you should add dependencies between the Modules.

C. Above is the answer

A. Same as ECS with local replica but synchronization logic is separate

B. Pro: Code ^ independenc

C. Consumers of CS is not affected by Syn

D. Sync can orchestrate several CS

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

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

G. Same as Base ECS pattern, but have a local replic

H. Store data to serve as a local cach

I. Pro: Leverage Entity Use, Simpler Integration AP

J. Con: Less impact on source system

K. ... caches only summary data that is frequently lister, joined or searche

L. Full detail for a O single entry is fetched directly from external syste

M. Use when whole database too big or costly to synchroniz

N. Details are only required for single entities (not lists)

O. ... Entity is not in Outsystems but in an external ERP syste

P. IS just makes remote call to p external system/databas

Q. No data is being kept inside O

R. Data retrieval may not be optimized as it needs to traverse two different systems to get the information bac

S. Con: Integration API must support all use cases

T. ... tries to fetch data from local cache entity, if not there, get single entry from the external v syste

. Cache only that record (read-through caching) Use when whole database too big or costly to synchroniz

. Integration only touches a small portion of the databas

. Avoid if access to lists of data is needed up front

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

. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

. ... is needed if data is coming from MULTIPLE external system

. IS will decide which driver to use depending on the data.

A. A BL becomes a Calculation Engine if it performs complex calculations, (e.

B. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

C. Logic to Synchronize data in CS's with an external syste

D. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

E. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.

F. Reusable Core Services with public entities, actions, and blocks.

G. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

A. End-User Application.

B. Foundation Application.

C. Core Application.