# cronos-architecture

> Overview of the CRONOS system design and inter-service communication

- Author: alfcalo
- Repository: alfcalo/cronos-app
- Version: 20260204115155
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/alfcalo/cronos-app
- Web: https://mule.run/skillshub/@@alfcalo/cronos-app~cronos-architecture:20260204115155

---

---
name: cronos-architecture
description: Overview of the CRONOS system design and inter-service communication
---

# CRONOS System Architecture

CRONOS is an integrated management system designed for medical or service-based clinics.

## Core Modules

1.  **Módulo de Caja (Cashier)**: Manages payments, billing, and daily closing.
2.  **CRM de Clientes**: Patient/Client profiles, history, and engagement tracking.
3.  **Calendario de Citas (Appointments)**: Scheduling, specialist availability, and alerts.

## Technology Stack

- **Backend**: Python (FastAPI, SQLAlchemy)
- **Frontend**: Next.js 14+ (App Router, TypeScript)
- **Database**: PostgreSQL
- **Containerization**: Docker & Docker Compose

## Communication Flow

All modules communicate through the shared PostgreSQL database. Frontend interaction is facilitated via REST APIs provided by the FastAPI backend.

### Architectural Rules
- **Decoupling**: Business logic should reside in the `services/` layer of the backend.
- **SSOT**: The database is the Single Source of Truth for all entity states.
- **Security**: Next.js Server Components and Server Actions must validate permissions before executing logic.