Denis Database

A lightweight Java cache and data engine

This site turns the project’s scattered README information into a clearer product-style documentation experience.

Introduction

Denis Database documentation

Denis Database is a Java-based data engine positioned around Redis-like simplicity, temporary data access, and lightweight operational workflows. The upstream repository mixes product notes, runtime scripts, SQL examples, and action class snippets; this site reorganizes those pieces into a cleaner, practical manual.

What Denis is

Based on the repository README and project structure, Denis is not just a library. It behaves more like a small runtime package with an embeddable Java core, command-line tools, and a server mode.

Redis-like workflow

Denis presents itself as a simple cache-first engine focused on temporary data manipulation and quick CRUD-style access patterns.

Multiple access surfaces

The repository exposes a packaged jar, CLI commands, service helpers, and a TCP server mode instead of only a single embedded API.

Hybrid query model

Beyond action classes such as actString and actStrist, the project also documents a SQL-like command subset for remote interaction.

Release-friendly install flow

The repo includes install scripts, start scripts, and bundled runtime files so users can run Denis outside a Java IDE.

Runtime-oriented packaging

Configuration and runtime files such as denis.toml, ddb.json, pawd.dat, and logs are expected to live next to the installed app.

Documentation gap

The upstream README covers key topics, but they are unevenly structured. This site normalizes them into a clearer learning path.

Who this documentation is for

This documentation is designed for developers evaluating the project, running a release build, or trying to understand how Denis exposes data through CLI, runtime files, and SQL-like commands.

Use Quick Start if you want to build and run Denis immediately from source.
Use Installation if you plan to install a release bundle on Linux or Windows.
Use CLI Commands if you need the operational entry points for version, server, and token commands.
Use SQL Queries and Action Classes if you want the supported interaction surfaces documented in one place.

Fastest way to validate the project

The repository README points to a local Maven build followed by direct jar execution.

mvn package

java -jar target/denis-0.0.2.9-alpha.jar --help
java -jar target/denis-0.0.2.9-alpha.jar server
java -jar target/denis-0.0.2.9-alpha.jar cli

Most useful runtime commands

These are the CLI examples that matter first when you are validating a release install or a local build.

denis --version
denis server
denis cli
denis cli --help
denis cli token -l
denis cli token -c