Marketplace Application composition

Edit on GitHub

The following document shows how Spryker Marketplace looks in general. As a result of reading this document, you will have a better understanding of what the Spryker Marketplace looks like on an application level.

Composition of the Applications

The following diagram illustrates how the application is composed. It is intentionally simplified, see Marketplace infrastructure system requirements for more details.

Applications composition

Storefront API

Storefront API is a REST API-based storefront application for customers. This is where customers browse the catalog and place orders.

Yves

Yves is a customer-facing HTML-based storefront application where customers browse the catalog and place orders.

Backend Gateway

Backend Gateway is a Storefront-oriented application. This is where a storefront (Yves/Glue) changes the state of the system (stock reservations, order placement, payments, etc.).

Merchant Portal

Merchant Portal is a merchant-focused application. Merchants use this system to manage their catalog and fulfill customer orders. Check out Merchant Portal’s architecture for more details.

Marketplace Operator Back Office

Back Office for the Marketplace Operator is a marketplace owner-centric or admin-centric application. Marketplace Operator here takes care of the whole Marketplace, including listing global products, managing merchants, and managing categories.

The Back Office also includes facilities oriented to the Operator-As-A-Merchant case, such as offers and orders management. Check out Marketplace in Back Office for more details.

Important Note

Ensure that Back Office is protected by a secure VPN connection.