Which of the following is a best practice for Adobe Commerce API design?

Question

Options

• AExpose database table structures directly
• BForce clients to use GraphQL
• CUse custom SQL statements instead of standard APIs
• DIntegrate multiple services via API Mesh

• A
  7% (3)
• B
  14% (6)
• C
  2% (1)
• D
  77% (34)

Explanation

API Mesh (option D) is correct because it is an Adobe-endorsed architectural pattern that allows developers to combine multiple APIs - REST, GraphQL, third-party services - into a single unified endpoint, reducing client complexity and following Adobe's official extensibility guidance.

Why the distractors are wrong:

• A (Expose database table structures): This is a major anti-pattern. Exposing raw DB schemas creates tight coupling, breaks encapsulation, and creates security and maintainability risks.
• B (Force clients to use GraphQL): Adobe Commerce supports both REST and GraphQL. Forcing one protocol limits interoperability; good API design offers flexibility.
• C (Custom SQL instead of standard APIs): Bypassing the service layer breaks the repository pattern, ignores ORM protections, and makes upgrades/customizations fragile.

Memory tip: Think of API Mesh as a "traffic controller" - it's Adobe's way of letting you plug multiple services together cleanly at the edge, rather than hacking the core. If an answer involves combining/orchestrating services through an official Adobe tool, it's almost always the best practice choice.

No community discussion yet for this question.