search

magento / architecture

A place where Magento architectural discussions happen
275 stars 155 forks source link

Admin Panel Configuration propagation to Storefront #402

Closed buskamuza closed 4 years ago

buskamuza commented 4 years ago

Problem

Existing Magento monolith is responsible for the whole cycle of data and user workflow. Magento Admin Panel contains configuration settings for all areas of the application, including Admin Panel behavior, storefront UI, etc.

With Storefront being a separate service (or set of services), should configuration settings in Magento Admin Panel be propagated to storefront service? If yes, in what way?

Task: https://github.com/magento/catalog-storefront/issues/154

Solution

Each case will be different and will require dedicated attention. Provided are guidelines on how to make a decision in each such case.

buskamuza commented 4 years ago

In stock/out of stock. @kokoc : keep out of stock products in Catalog SF due to big effort of recalculating product data when it gets back in stock (prices, etc).

Looks like this is config for option 2 - data config.

buskamuza commented 4 years ago

@kokoc : put config (such as in/out of stock) to the deployment phase, to env vars. - @buskamuza : to be covered in a follow-up proposal and discussion to not explode scope for the current discussion.

Task - https://github.com/magento/catalog-storefront/issues/171

buskamuza commented 4 years ago

Option 3:

  1. UI Config is responsibility of the client (PWA, etc)
  2. UI Config is provided by Magento Back Office API (GraphQL) proxied by GraphQL
  3. Current option 3.3.

Prioritized in the provided order. Agree with PWA, AEM teams what will be satisfactory.