Architecture
oCore system architecture, service layers, and design decisions
Deep dive into oCore's technical architecture. This section documents the internal service layer design, database schema conventions, and the patterns that hold the system together.
oCore is built on a Go + Echo backend, Next.js + React frontend, PostgreSQL database with Ent as the ORM, and River for background job processing. The backend follows a handler-service-repository pattern with strict separation of concerns.
Service Layer
Detailed documentation of all 50+ services, their responsibilities, dependencies, transaction patterns, and error handling conventions.
Ent Schemas
Database schema conventions including UUID primary keys, timestamps, soft deletes, and privacy rules across 83 Ent schemas.
Related
The Developer Guide covers these topics from a practical development perspective:
- Architecture Overview -- High-level system architecture with Mermaid diagrams
- Backend Development -- Handler-Service-Ent pattern and adding new endpoints
- Job Queue -- River job queue internals and worker patterns
- Middleware Chain -- Authentication, tenant isolation, and RBAC