Engines / Guides
Guides
The Guides cover TinyStore one engine at a time, for when you know what you need: how keys expire, how a job retries, how a search filters. Each engine has an overview, then a page per feature, every example in TypeScript, Python, Go and Rust. The Handbook explains the same engines as parts of one application, and why they work as they do.
| Engine | For | In the Handbook |
|---|---|---|
| SQL | your own SQLite databases: migrations, queries, transactions | Messages |
| KV | values with expiry and versions; counters, rate limits, quotas, once | Sessions and limits |
| Jobs | work later or on a schedule, retried, with steps | Replies in the background |
| Blobs | files by path, written whole, checked when read | Attachments |
| Search | words in any language, typos, vectors, filters | Finding old messages |
| Channels | messages to whoever listens now | Live updates |
| Locks | one holder of a key at a time, with fences | Live updates |
| Config | settings from files and the environment, some changed live | Settings |
| Records | logs and events, kept and read back | What it is doing |
| Metrics | counters, gauges, timers and histograms, read exactly | How fast it is |
| Backup | the whole store as one checked zip, taken while it runs | Keeping it |
The command line has a guide of its own: serving a store, reading it while it runs, backups and nodes.
Every engine opens from the store, which Your first store opens in each language. A program reaches the store in its own process, through a sidecar, a private child or a server on another machine: Connecting compares the four.