Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

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

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

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

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

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

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

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

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

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

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

Discuss OutSystems Architecture-Specialist-11 Exam Topic 1 Question 8

DE

Denny 11 months ago

Nah, I don’t think A works here. It’s not really about lazy loading.

VI

Viola 11 months ago

I’m surprised by how many options there are! This is confusing.

AR

Arlette 11 months ago

Wait, isn’t A also a good match? It talks about caching too.

EM

Emiko 12 months ago

Totally agree with E! It’s all about fetching only what you need.

LU

Luz 12 months ago

I think E is the right choice. It fits the lazy load concept well.

CH

Cheryll 1 year ago

I recall that Lazy Load is about minimizing data transfer, so option E sounds familiar, but I’m worried I might be mixing it up with something else.

RE

Reuben 1 year ago

I’m leaning towards option C since it mentions having a local replica, but I’m not confident if that’s the right match for Lazy Load.

ER

Erick 1 year ago

I remember practicing a question similar to this, and I feel like option A might fit because it talks about caching summary data and fetching details on demand.

JU

Junita 1 year ago

I think the ECS Lazy Load variation is about fetching data only when needed, so maybe option E? But I'm not entirely sure.

AR

Arlie 1 year ago

This question is really testing our knowledge of the different ECS patterns and their variations. I'm not as familiar with the "ECS Lazy Load" specifically, but based on the descriptions, I think option A sounds the most like it. It talks about caching only summary data and fetching full details from the external system as needed, which seems to align with the lazy loading concept.

VE

Venita 1 year ago

Okay, I think I've got this. The "ECS Lazy Load" variation is the one that tries to fetch data from a local cache first, and only goes to the external system if the data isn't found in the cache. That sounds like option E, which describes a read-through caching approach. I'm pretty confident that's the right answer.

DO

Donte 1 year ago

Hmm, this is a tricky one. The question is asking about a specific variation of the Core Module Pattern, and there are a lot of options to choose from. I'm a bit unsure about the differences between some of these, like the "ECS with local replica" and the "ECS Lazy Load" variations. I'll need to re-read the descriptions carefully to try to identify the right match.

AL

Alecia 1 year ago

This question seems to be testing our understanding of the different variations of the Core Module Pattern in the ECS (Entity-Connector-Sync) architecture. I think I have a good grasp of the concepts, so I'll carefully read through the options and try to identify the one that best matches the "ECS Lazy Load" variation.

LA

Lamar 1 year ago

Hmm, I'm not sure about this one. I think it might be D - the supervisor can add gadgets to the agents' desktops. But I'm not 100% confident on that.

MI

Mirta 1 year ago

I'm a bit confused by the wording of the question. I'll need to read it over a few times to make sure I understand the options.

LA

Laurel 1 year ago

I definitely remember that #FFFFFF stands for white, so I'd go with C for this question!

CH

Chandra 3 years ago

Ooh, good point! I didn't notice the 'Core Module Pattern' part before. G) does seem to be a closer match, with the mention of the local replica and the separation of the synchronization logic. E) is more of a standalone caching pattern, while G) feels more like a variation on the core ECS pattern.

GL

Glory 3 years ago

You know, the more I think about it, the more I'm leaning towards G) as well. The 'code independence' and 'consumers not affected by Sync' aspects sound like they could be key features of the 'Lazy Load' variation. Plus, the 'ECS with local replica' part seems to fit the 'Core Module Pattern' description.

BR

Brynn 3 years ago

↳ replying to Glory

Absolutely. The 'Lazy Load' aspect seems to be well represented in G) with the separated synchronization logic and local replica.

MA

Malinda 3 years ago

↳ replying to Glory

True. It could help improve performance and reduce the need for constant external calls.

WA

Wade 3 years ago

↳ replying to Glory

That makes sense. Plus, having the local replica in G) aligns with the idea of storing data for quicker access.

FL

Fletcher 3 years ago

↳ replying to Glory

Definitely. It seems like it would make the system more resilient to changes in synchronization.

VI

Vicki 3 years ago

↳ replying to Glory

Yeah, I agree. The separation of synchronization logic in G) does sound like it could lead to code independence and less impact on consumers.

FR

Francoise 3 years ago

↳ replying to Glory

I think G) could be a good match for the Core Module Pattern - ECS Lazy Load variation.

OutSystems Architecture-Specialist-11 Exam - Topic 1 Question 8 Discussion