Would using many engine instances nested within each other on the same page cause performance problems?

Client
, , ,
1

Suppose I would like to create a page for editing cart item quantities in an ecommerce application. If the page would consist of nested engine instances to present different parts of the data to the user, would this introduce a performance problem?

For example I would like to use the Content Engine for the presentation of the cart but would have a Content Engine Fragment displaying a Form Engine for each item in the cart to allow editing of that items quantity.
Or I would like to use the Overview Engine to display the cart items and would nest a Content Engine for each cart item to display details of the items product.

The above is supposed to perform reasonably well on devices like tablets or low budget laptops. The number of diffrent items per cart would be in the range of about 100.

2

Hi,

Skipping the current support limitation for multiple instances of the Overview/Form Engine, the Content Engine is just another way to write a React component; therefore, I do not think using the Content Engine could introduce any critical performance issues compared to calling React components directly.

3

Thanks for your response @nam-secure-mesa.

Can you please explain what the

is? Is this mentioned somewhere in the geta12 docs?

4

Hi @andreas-fresh-mesa , for the Overview Engine that displays a UI other than table rows, such as tiles, you can pass your tile list inside the Overview Engine component without any issues. However, you will need to handle the events (like row actions) yourself, especially if you want to integrate with the pure Content Engine. This is because we do not support event handling for static pages (which is the current primary target of the engine) at least until 2024.06-ext2.

Hi @erik-radiant-gorge, can you please take a look and maybe answer the FE part? :smiley:

5

I don’t think that a severe performance issue will arise if you try to nest form engines.

However, achieving this nesting in the first place will be the real issue.
At the moment, the form engine expects to own the data and UI settings in an activity.
When nesting, each engine needs to have its separate slice of data and UI settings within the same activity. This will probably be complex to setup with our current APIs.

Furthermore I want to add that we are already working on a broader topic with the goal of achieving exactly this: composition or nesting of engines within content model pages.