Skip to content

MVP Architecture

Garot Conklin edited this page Dec 26, 2024 · 1 revision

MVP Architecture

Overview

RunOn MVP follows a clean, backend-first architecture focusing on core functionality and testability.

Backend Architecture

Core Components

backend/
├── functions/           # Core business logic
│   ├── event_discovery/ # Event search functionality
│   └── calendar_sync/   # Calendar integration
├── models/             # Data models
│   └── event.py        # Event data structure
└── tests/              # Test suite
    ├── event_discovery/
    ├── calendar_sync/
    └── models/

Data Flow

graph TD
    A[Event Discovery] --> B[Models]
    C[Calendar Sync] --> B[Models]
    B --> D[Tests]
    A --> D
    C --> D
Loading

Testing Strategy

  • 100% code coverage requirement
  • Integration with SonarCloud
  • Automated testing via GitHub Actions
  • Comprehensive test suite:
    tests/
    ├── event_discovery/   # Event search tests
    ├── calendar_sync/     # Calendar integration tests
    ├── models/           # Data model tests
    └── conftest.py       # Test configuration
    

CI/CD Pipeline

Workflow:
  build:
    - Python setup
    - Install dependencies
    - Run tests
    - Generate coverage
    - SonarCloud analysis

External Dependencies

  • Google Search API
  • Google Calendar API
  • SonarCloud
  • GitHub Actions

RunOn Documentation

MVP Documentation

Core Documentation

Archived (Full-Featured)

Full-Featured Documentation

Clone this wiki locally