Java Backend Demo

Expiring Key-Value Store

Interactive UI for a TTL-based key-value service. This demo lets you create entries, conditionally write if absent, fetch current values with remaining TTL, delete keys, and inspect a live snapshot of the store.

View developer notes ↓

Endpoints

PUT · GET · DELETE

Core Behavior

TTL · Expiration · Snapshot

Stack

Spring Boot · Java

Request Builder

Run store operations

Store Snapshot

Inspect current entries

Load the snapshot to inspect active store entries.

Developer Notes

Expiring Key-Value Store Demo

This page demonstrates a backend-driven TTL store where key state lives entirely on the server. The UI is intentionally thin: it builds requests, renders results, and treats the Java service as the source of truth for expiration, conditional writes, and live snapshots.

Endpoints

  • PUT /entries/{key} stores or overwrites a value with TTL.
  • PUT /entries/{key}/if-absent writes only when the key does not exist.
  • GET /entries/{key} returns the value and remaining TTL.
  • DELETE /entries/{key} removes a key.
  • GET /snapshot returns a point-in-time view of the store.

Core Behaviors

  • Time-to-live is set per entry in milliseconds.
  • Expired keys behave as absent keys during reads.
  • Conditional insert semantics support race-aware write flows.
  • Snapshot inspection helps visualize server-side store state.

UI Design Notes

  • Request controls are grouped by operation to make endpoint behavior explicit.
  • The request preview mirrors the exact route currently being targeted.
  • The UI separates direct key operations from global store inspection.