Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation

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

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

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

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

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

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

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

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

I) ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to . 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

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

Discuss OutSystems Architecture-Specialist-11 Exam Topic 2 Question 30

JU

Justine 11 months ago

H sounds interesting, but how does it handle external libraries?

EV

Eva 11 months ago

I feel like C has a strong case too, with the sync logic separation.

PA

Pansy 11 months ago

Wait, isn't option G more about local caching?

MA

Man 12 months ago

Totally agree, B is spot on for caching summary info!

SH

Sherly 12 months ago

I think option B fits best, it focuses on summary data.

ER

Ernest 12 months ago

I have a feeling that option A is too similar to the base ECS pattern, but I’m not sure if it aligns with the summary cache variation.

NI

Nichelle 1 year ago

I'm a bit confused about option C and D. They both mention local replicas, but I can't recall the specific differences between them.

DO

Dorinda 1 year ago

I remember practicing a question similar to this, and I feel like option G might be relevant too, since it mentions fetching from a local cache first.

BR

Brande 1 year ago

I think option B sounds familiar, especially the part about caching summary data. It seems to fit the ECS summary cache concept, but I'm not entirely sure.

JA

Jaleesa 1 year ago

I think I've got a good handle on the key elements of the Core Module Pattern - ECS Summary Cache only variation. Now it's just a matter of carefully analyzing each option and selecting the one that best matches those characteristics.

CE

Celia 1 year ago

Option G seems to be describing a read-through caching approach, which could be a valid variation of the ECS pattern. I'll make sure to consider that as a possibility, along with the other options that more directly mention the "summary cache" aspect.

KI

Kirk 1 year ago

I'm a bit confused by some of the options, like C and D. They mention additional features like separate synchronization logic and an API module, which don't seem directly relevant to the specific pattern described in the question. I'll need to focus on the core characteristics of the pattern.

LU

Lucina 1 year ago

Option B looks like the best match to me. It mentions caching only summary data that is frequently used, while fetching full details directly from the external system as needed. That aligns with the "ECS Summary Cache only" part of the question.

CA

Casie 1 year ago

This question seems straightforward, but I want to make sure I understand the key differences between the patterns. I'll need to carefully read through each option and think about how they align with the Core Module Pattern - ECS Summary Cache only variation.

KE

Kenda 1 year ago

The key here is understanding the relationship between the Oracle Adapters, OSB, and SOA Suite. Since the adapters are deployed on the same WebLogic servers, that's probably an important factor. And the XA features could also play a role in how they integrate.

GR

Gregoria 2 years ago

Option B is the way to go, folks. It's like a 'Cliff's Notes' version of the external system - just the highlights, without all the fluff.

TW

Twanna 2 years ago

Option H is just too weird. 'A wrapper used to contain the logic, actions and data that will expose code that is inside of external library'? What does that even mean?

SA

Sanda 2 years ago

↳ replying to Twanna

I think option H is trying to abstract away the complexity of interacting with external libraries or databases.

TH

Thad 2 years ago

↳ replying to Twanna

Yeah, I agree. Option H seems like it's trying to do too many things at once.

EZ

Ezekiel 2 years ago

↳ replying to Twanna

I know, option H does sound confusing. It's like a wrapper for a wrapper.

EL

Elena 2 years ago

Option J is a bit too generic. It's talking about a connector and wrapper module, but doesn't really address the specific ECS summary cache pattern.

TE

Terina 2 years ago

Option I looks interesting, but it doesn't seem to fit the 'ECS Summary Cache only' requirement. It's more about just making remote calls without any local caching.

EN

Enola 2 years ago

↳ replying to Terina

We should look for an option that includes local caching for the ECS Summary Cache pattern.

RU

Ruth 2 years ago

↳ replying to Terina

Yeah, option I seems to focus more on remote calls without local caching.

DA

Dalene 2 years ago

↳ replying to Terina

I think option I is not the right fit for the ECS Summary Cache only requirement.

VA

Val 2 years ago

I'm leaning towards Option G. It describes a read-through caching approach, which aligns with the 'ECS Summary Cache only' variation.

CA

Carlton 2 years ago

↳ replying to Val

Yes, it would help optimize data retrieval and avoid syncing the entire database.

OR

Oren 2 years ago

↳ replying to Val

I agree, read-through caching would be beneficial for this pattern.

FR

Franklyn 2 years ago

↳ replying to Val

Option G seems like a good fit for the ECS Summary Cache only variation.

DI

Diego 2 years ago

I'm leaning towards answer C. Separating synchronization logic could provide more flexibility in the long run.

WA

Wai 2 years ago

I disagree, I believe the answer is G. Fetching data from local cache first can be more efficient.

LI

Lizette 2 years ago

Option B seems to be the best match. It specifically mentions caching only the summary data and fetching the full details from the external system when needed.

SO

Solange 2 years ago

↳ replying to Lizette

Yes, option B is the most suitable for the Core Module Pattern - ECS Summary Cache only variation.

WY

Wynell 2 years ago

↳ replying to Lizette

Option B seems like a good choice, it focuses on caching summary data and fetching details when necessary.

AN

Annamae 2 years ago

↳ replying to Lizette

I agree, option B mentions caching only summary data and fetching full details when needed.

NA

Narcisa 2 years ago

↳ replying to Lizette

I think option B is the best match for Core Module Pattern - ECS Summary Cache only variation.

RE

Ressie 2 years ago

↳ replying to Lizette

I agree, Option B mentions caching only summary data and fetching full details when needed from the external system.

MA

Malcolm 2 years ago

↳ replying to Lizette

I think Option B is the best match for Core Module Pattern - ECS Summary Cache only variation.

ER

Erinn 2 years ago

I think the answer is A. Having a local replica for caching seems like a good idea.

OutSystems Architecture-Specialist-11 Exam - Topic 2 Question 30 Discussion