NenuDB
- NenuDB is the embedded, purpose-built database engine developed for durable application state in App Marché.
- It keeps typed entity records, declared indexes, queries, grouped changes, and recovery under one storage boundary.
- The current engine can open consistent earlier views and restore earlier state onto a new timeline without overwriting what came later.
What NenuDB Is
NenuDB is a database engine designed and built by Nenu for App Marché. It runs with the application backend and persists the entity records that must survive beyond a request, browser session, or process restart. It owns the storage concerns around durability, indexing, history, recovery, and the lifecycle of application state.
NenuDB is especially suited to structured operational data: records an application creates, changes, finds, counts, and revisits throughout its life. Numeric values and ranges are first-class query targets, but NenuDB is not limited to counters or numbers; it stores complete typed application records.
What It Can Do
| Capability | What it means for an application |
|---|---|
| Typed records and schema awareness | Keep entity records aligned with the shapes and index declarations the application defines. |
| Durable operations and recovery | Persist accepted changes across restarts and recover only verified durable state after an unexpected interruption. |
| Unique and indexed retrieval | Find records by identity, unique fields, or other declared exact-match indexes. |
| Numeric range queries | Find records whose numeric values fall within a selected range. |
| Paging and counts | Work through larger result sets in bounded pages and count matching records. |
| Grouped record changes | Apply changes to multiple records in one entity as one durable group. |
| Point-in-time views | Open a record, one entity, or the whole database at the latest accepted state at or before an earlier time. |
| Non-destructive restoration | Restore a whole database or one entity onto a new writable timeline while preserving the later state on the original timeline. |
| Whole-database backup and restore | Capture and restore a consistent database as one operational unit. |
Current State And History
For current state, NenuDB supports creating, reading, updating, deleting, querying, paging, and counting typed entity records. App Marché developers reach those capabilities through entities and backend workflows while the platform owns the storage connection.
The current NenuDB engine also supports point-in-time records, entity views, consistent database views, and restoration onto a new timeline. These are engine capabilities; App Marché decides how and when they appear in product workflows.
Where It Fits
NenuDB is designed for typed operational state that an application must remember, query, change safely, and sometimes revisit. That includes ordinary entity records as well as data with important numeric values or ranges.
- Accounts, projects, work items, orders, and workflow records.
- Inventory, balances, counters, scores, progress, and usage totals.
- Statuses and records retrieved through unique or indexed fields.
- Application state that benefits from historical inspection, backup, or restoration.
How Developers Use It
App Marché developers normally use NenuDB through entities, data queries, and backend workflows rather than managing storage directly. NenuDB remains a standalone database engine beneath that platform boundary, while App Marché owns access control, product workflows, and the connection between application logic and storage.