Public Access

Files

gramps 2a9afe7d77 Add MariaDB IPL validation, topology docs in beds.toml, and developer wiki

- Add MariaDB (REL) IPL validation — master required, secondary non-fatal
- Add RelNodeConfig / RelInstanceConfig structs with master/secondary pattern
- Add rel_services section to beds.toml and test fixture
- Add detailed topology commentary to beds.toml covering standalone,
  master/replica, Galera cluster, and multi-DB-per-node configurations
- Add developer wiki (wiki/) covering:
    - Origin story — PHP Namaste history, production record, why Rust
    - Architecture overview — full system diagram, all layers explained
    - The four nodes — appServer, admin, segundo, tercero with real-world context
    - IPL sequence — every step documented with rationale for ordering
    - Configuration system — layering, env selection, adding new sections
    - Queue topology — exchanges, routing keys, broker bindings, vhost isolation
    - Template system — REC/REL, TLA convention, cache map, warehousing
    - Event lineage — compound event IDs, parent/child tracking, msLogs schema
    - Glossary
- Update README with wiki index and MariaDB status

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-04 15:41:28 -07:00

1.9 KiB

Raw Blame History

BEDS — Back End Data System

Developer Wiki

Welcome to the BEDS developer wiki. This is a living document. It grows with the codebase and should be updated whenever a design decision is made, a pattern is established, or a component is implemented.

If you are reading this as a new contributor, start here and read in order. The origin story is not fluff — it explains why BEDS is built the way it is, and understanding the why is the difference between extending the framework correctly and breaking it subtly.

Foundation

Origin Story — Where BEDS came from and why it was built
Architecture Overview — The full system design and its principles
The Four Nodes — appServer, admin, segundo, tercero — roles and responsibilities

Operations

IPL — Initial Program Load — The bootstrap sequence, step by step, and why order matters
Configuration System — Layered TOML, environment files, topology options

Messaging

Queue Topology — AMQP exchanges, queues, routing keys, and the broker model
Broker Calls — Every broker event type documented

Data

Template System — REC and REL templates, the TLA convention, schema-as-contract
Event Lineage — Compound event IDs, parent/child relationships, depth tracking

Reference

Glossary — Terms, abbreviations, and conventions used throughout BEDS

Contributing to This Wiki

Write for the programmer who inherits this code after a two-week handoff with no knowledge transfer
Document decisions, not just mechanics — why matters more than what
Dated history entries belong in source code comments, not here — the wiki covers concepts, not changelogs
When you change the system, update the wiki in the same commit

1.9 KiB Raw Blame History