How cbnsndwch/rocicorp-mono works
High-Level Architecture Overview
┌─ Rocicorp Monorepo ─────────────────────┐
• ┌─ Zero ──────────┐ ┌─ Replicache ─┐ │
• Modern Database │ │ Sync Engine │ │
• ┘ └─────────────┘ │
• ┘
Zero Product Architecture
a) Client-side components:
• zero-client (main client library)
• zero-react (React integration)
• zero-solid (Solid.js integration)
• zero-schema (schema definition)
b) Server-side components:
• zero-cache (server implementation)
• zql (query engine with IVM)
• zqlite (SQLite integration)
• Blue rectangles for client-side components
• Green rectangles for server-side components
• Yellow diamonds for data stores
• Red hexagons for query engines
Replicache Architecture
• Client library components
• Documentation system
• Integration points with Zero
• Sync engine components
• Data flow patterns
Specific Implementation Details
Technical details such as:
• WebSocket connections for real-time updates
• SQLite storage on the client
• PostgreSQL integration on the server
• Authentication flows
• Cache invalidation patterns
Development and Deployment
CI/CD pipeline using the configuration from .github/workflows:
• Bundle size monitoring
• Cloudflare deployment
• Performance testing
• Mirror operations
Key Elements to Include:
Data Flow
Client ←→ WebSocket ←→ Server ←→ Database
Component Relationships
zero-client → zero-cache → zql → database
Integration Points
Applications (zbugs) → zero-client → Replicache
Deployment Architecture
GitHub → CI/CD → Cloudflare/Production
Use standardized symbols:
• 📦 for packages
• 🔄 for sync operations
• 💾 for storage
• 🔌 for integrations
• 🔒 for security/auth
Development and deployment workflows
Tools Recommendation:
• Version control integration
• Component reuse
• Clear visual hierarchy
• Standard notation
Remember to maintain consistency in:
This architecture should clearly show how the monorepo's components work together while maintaining separation of concerns and highlighting the unique features of both Zero and Replicache products.