WOWW DOCUMENTATION
Database & storage
Choose persistence for metadata, repositories, caches, object storage and search indexes.
Separate data classes
| Data | Common choice | Notes |
|---|---|---|
| Application metadata | PostgreSQL | Transactions, migrations and tested restore |
| Cache / queues | Redis | Do not use cache as the only durable copy |
| Git repositories | Local SSD or managed Git storage | Replication, snapshots and integrity checks |
| LFS / packages | S3-compatible object storage | Encryption, lifecycle and access policies |
| Code search | OpenSearch / Elasticsearch | Secure cluster; index is rebuildable |
Object storage checklist
- Use a dedicated bucket and least-privilege key.
- Enable encryption at rest and TLS in transit.
- Configure versioning and lifecycle rules.
- Keep credentials in a secret manager.
- Test multipart upload and checksum validation.
WOWW framework does not bundle a database, Git hosting storage engine, search engine or migration runner.
Scope note: WOWW 0.2.0 is a framework package. Hosted Git collaboration, account management, Copilot plans, hosted runners, public REST/GraphQL services and a
woww/core server image are not included. The related guidance below is architecture or integration advice, not a claim that those services are live.