Expand my Community achievements bar.

Implementing Adobe Commerce on Edge Delivery Services: Addressing Unsupported Components, Live Search Integration, and API Mesh Usage

Avatar

Level 3

Hello community,

 

I’m planning an implementation of Adobe Commerce on Edge Delivery Services and have some specific questions that I hope you can help clarify:

 

Unsupported "drop-in" components :

 

In the documentation, some components listed under "Commerce drop-in components" are not marked as supported. What approach does Adobe recommend for addressing these cases in a project?

 

Is there a public roadmap detailing when support for these components is planned? If so, where can it be accessed?

 

Storefront Services and Live Search:

 

Is Live Search mandatory in Storefront Services?

 

If Live Search is not implemented, what key functionalities would be lost or limited?

 

Is it possible to use alternative solutions like OpenSearch to meet these needs?

 

API Mesh for integrations:

 

According to the note in the documentation, API Mesh for Adobe Developer App Builder allows aggregating multiple APIs. Is it feasible to implement this layer between the storefront and external services for scenarios requiring third-party system integrations (e.g., alternative search engines or custom tools)?

 

I would greatly appreciate practical examples, links to relevant documentation, or experiences from other users who have faced similar challenges.

Thank you in advance!

 

Storefront architecture | Adobe Commerce Storefront

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies