Frontend

Backend for Frontend

Understanding the basics of Orchestr

Introduction

Orchestr is the powerful data-composition framework at the heart of Laioutr. It is designed to be a flexible and powerful tool for building scalable data layer applications with a focus on type safety, data composition, and modular architecture.

Core Concepts

Orchestr is built around four main handler types that work together to provide a complete data layer solution:

Action Handlers: Handle mutations and side effects
Query Handlers: Fetch and return entity IDs
- Query Templates: Preview data for queries in the Studio
Link Handlers: Define relationships between entities
Component Resolvers: Resolve specific data components for entities

Orchestr caches API data at three levels (queries, links, component resolvers) to reduce latency and backend load. See Caching for strategies, cache keys, and how to use the cache in your own handlers.

Tokens

As orchestr does not know which app is responsible for a given action, query, link, or component, it uses tokens to identify them.

Tokens can be thought of as "contracts" between the frontend, orchestr and the apps. Each token is a unique identifier that is used to identify the action, query, link, or component.

Action Token

Defines the input and output of an action. Typically used for mutations and side effects like creating an order, adding an item to a cart, etc.

Query Token

Defines the input of a query. Typically used for fetching data from the database. E.g search for products by a string, show products in category.

Link Token

Defines the input a link. Similarly to queries, these can be called on entities to fetch related entities. E.g. get all variants of a product, get all orders for a customer.

Component Token

Defines the schema of a entity component. Entity components describe a subset of data of an entity. E.g. product-prices, category-seo, etc.

Edit this pageorReport an issue

Sitemap

Generate XML sitemaps for your Laioutr frontend to help search engines discover and index your pages. Automatically includes pages from your runtime config and integrates with robots.txt.

Recipes

Patterns and gotchas from building connectors against real commerce backends. Each recipe captures one problem we hit and the approach that worked.