Drop DynamoDB from scope

Was originally a proof of concept in the PHP version. Dropped in
production as too expensive. Removed all references from docs.
Supported backends are MySQL/MariaDB and MongoDB only.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-03-31 11:06:20 -07:00
parent c87c3f1bac
commit 850993edb1
2 changed files with 9 additions and 10 deletions

View File

@@ -38,7 +38,7 @@ Client Request
NamasteCore Trait (unified CRUD interface)
Database Adapter (MySQL · MongoDB · DynamoDB)
Database Adapter (MySQL · MongoDB)
DBA-owned Schema (views · stored procedures · functions)
@@ -51,7 +51,7 @@ Client Request
## Core Principles
1. **AMQP-first** — all data access flows through the broker layer, no exceptions
2. **Database agnostic** — MySQL/MariaDB, MongoDB, and DynamoDB behind a unified trait; no DB-specific logic leaks upward
2. **Database agnostic** — MySQL/MariaDB and MongoDB behind a unified trait; no DB-specific logic leaks upward
3. **DBA-owned schema** — all data access goes through named database objects; the application calls template names, not queries
4. **Template-driven CRUD** — each data domain is a struct implementing `NamasteCore`; adding a domain means adding one file
5. **Config-driven nodes** — all nodes run the same binary; role is determined entirely by startup config
@@ -125,7 +125,7 @@ The `config` crate deep-merges these at startup. Only keys present in `env.toml`
| Structured logging (journald + console) | Done |
| Broker pool | Next |
| NamasteCore trait | Planned |
| Database adapters (MySQL, MongoDB, DynamoDB) | Planned |
| Database adapters (MySQL, MongoDB) | Planned |
| Factory dispatch | Planned |
| AI database object generation | Phase 2 |