ActiveMemory the missing ORM for ETS and Mnesia
summary
Introduces the ActiveMemory hex package that wraps ETS and Mnesia into a familiar Store API with auto-generated UUIDs, migrations, match-style queries and seed loading; the Store runs as a Store backed by a GenServer but most operations hit ETS/Mnesia directly, includes a withdraw one-time-read operation, and an Amnesia manager that adds disk persistence and helps horizontal scaling. Benchmarks show a read penalty vs direct ETS (noticeable but far faster than a DB) while writes remain about the same; sample apps and repo are available.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:48Who is using ActiveMemory
- 1:11Why use ActiveMemory
- 1:53Database dependency
- 2:40Why ActiveMemory
- 3:58Delivery Trucks
- 4:58Use Cases
- 5:08Application Secrets and Settings
- 6:09OneTime Use Tokens
- 6:59API Keys
- 7:39JWT Encryption Keys
- 8:12Admin User Management
- 8:28Session Management
- 8:54Features
- 9:29Query syntax
- 10:04Store
- 10:39Seed File
- 11:02Before
- 11:21Initial State
- 11:52Amnesia Manager
- 13:22Mnesia Bench Tests
- 13:46Demo
- 15:01Future plans
- 16:37Questions
related talks
53mJava In-Memory Database-Apps with EclipseStore
57mJava In-Memory Database-Apps with EclipseStore
55mDatabaseless High-Performance Persistence with EclipseStore...
46mEdge Performance with In memory NoSQL
47mDesigning Great Java In-Memory Object Models
32mJava's Ignored Potential: Supercharge Database Apps with Java In-Memory Process
46mLeveraging ETS Effectively
48mIntroduction to EclipseStore Coding