Backend Recipes for a Data Grid

A grid connects to whatever already holds your data. These five guides each take one wire shape, show the full source of a small reference server where one exists, and say exactly what pushes to your backend against what the grid finishes on its own. The reference servers live in one public repository, MIT-licensed, with no keys and nothing that phones home: lattice-grid-backend-recipes.

• REST API paging for a data grid

  One JSON request in, { rows, total } back. The zero-setup Node and SQLite recipe, full source.

• SQL through your own endpoint

  A filter and a sort become one parameterised statement behind your own API, with a dialect appendix for MySQL, SQLite and SQL Server.

• GraphQL cursor paging for a data grid

  Point graphqlAdapter at a Relay-style connection and the grid walks it forward by cursor instead of by offset.

• Stream a feed into the Data Router

  One feed, many live grids: a partition value decides which view each record reaches, with a held backlog that bounds a busy one.

• A job-style search API for a data grid

  Submit a job, poll it, read a window once it is done. The shape splunkAdapter speaks against Splunk's own search REST API.

For the full request and answer shape every adapter here implements, see the pushdown developer guide; for a task-shaped, one-page example of a single grid feature rather than a backend, see the how-to guides.