To manage routing this functionality and adhere to best practice, you need to consider the following options:

• Create a standard controller route and an Index/Index index controller class that loads the relevant news article by matching the URL date and URL key parts. This option will create a simple and straightforward way to handle the news requests using the standard Magento routing mechanism. The Index/Index controller class will receive the date and URL key parameters from the request and use them to load the news article model from the database.
• Create a custom router that runs before the standard router and matches the news portion of the URL, then looks for and loads a news article by matching the date and URL key parts of the URL. This option will create a more flexible and customizable way to handle the news requests using a custom router class that implements \Magento\Framework\App\RouterInterface. The custom router class will check if the request path starts with news, then extract the date and URL key parts from the path and use them to load the news article model from the database.

Asynchronous indexing allows Magento to process indexers in the background without affecting the storefront performance. Splitting the database allows Magento to use a separate database for checkout-related tables, which reduces the load on the main database and improves checkout performance. References: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#asynchronous-indexing https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html

To decrease the impact on checkout performance, the Architect should do two things:

• Enable asynchronous indexing admin panel setting. This will allow Magento to update indexes using cron jobs instead of doing it on the fly during checkout. This option can be found under Stores > Settings > Configuration > Advanced > Developer > Grid Settings > Asynchronous indexing. It can also be enabled by executing the following CLI command: bin/magento config:set dev/grid/async_indexing 1
• Create a new database and use the Split Database feature. This will allow Magento to separate the sales data from the main database and reduce the load on the database server. This option can be configured with the following command: bin/magento setup:db-schema:split-sales --host=‘’ --dbname=‘’ --username=‘’ --password=‘’

References:

• https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde-asynchronous-indexing
• https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html

It will allow you to exclude logging observers from being executed during staging preview functionality by adding them to bannedObservers parameter of \Magento\staging\Model\Event\Manager type in di.xml file. This will prevent customer activity data from being logged while previewing storefront catalog pages from Admin Panel for a future scheduled campaign.

The Architect should check the list of logging observers in bannedObservers parameter of \Magento\Staging\Model\Event\Manager type in di.xml. This parameter defines the list of observers that should not be executed during staging preview. The Architect should add the logging observers to this list to prevent them from recording customer activity data while previewing the storefront catalog pages from Admin Panel. References: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/staging.html