Free ARCHITECTURE-SPECIALIST-11 Exam Dumps Preview

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

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

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

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 not in Outsystems but in an external ERP system. IS just makes remote call to p external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con:Integration API must support all use cases

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 upfront

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)

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

Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online.

Sync data required per use case: Sync summary data on session start. On data selection, sync its details.

A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

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

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

Ensuring order and sync granularity. Sync incrementally by entity with partial commits. This way, synchronizations are prepared for constant interruptions and allow retries without repeating the entire synchronization from the start.

REST API

Concepts are disclosed to the Architecture team

Concepts are assembled into Modules

Customer_CW

Mobile_API

Service_CS

Generic Library module.

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

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

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

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

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.

Supports Planning : Helps the team anticipate and build solutions

Drives Consensus : Helps create common ground with the team

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

technical wrapper to consume and normalize an external service.

Generic Library module.

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

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

Same as the Base ECS pattern, but with a local replica. Data is stored to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on the source system.

A pattern with two modules: a connector module that encapsulates an external API with the input/ output structures and a wrapper module to expose the normalized API to consumers.

Tries to fetch data from a local cache entity; if not found, it retrieves a single entry from the external
system. Only that record is cached (read-through caching). Use when: The database is too large or costly to synchronize, and integration only requires a small portion of the data. Avoid if: Access to lists of data is needed upfront.

Same as ECS with a local replica, but an API module is provided. This allows changes in the external system to notify OS, which then retrieves updates from the ERP system (subscription system).

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

A wrapper used to contain the logic, actions, and data that exposes code within an external library, or to inspect an external database and import the data structures so they can be used as entities within
OS.

Entity is not within Outsystems but resides in an external ERP system. IS makes remote calls to the external system/database. No data is stored inside OS. Con: Data retrieval may not be optimized as it traverses two systems. Integration API must support all use cases.

Used when data comes from multiple external systems. IS determines which driver to use based on the data.

End-User layer

Core layer

Assemble

Disclose

Organize