David
e94d5e6c71
- Created project overview document for UECKO application. - Added README file for project documentation structure. - Introduced template for architectural decision records (ADR). - Defined backend architecture guidelines. - Established conventions for project-wide consistency. - Documented data persistence architecture. - Outlined frontend architecture principles. - Developed testing strategy documentation. - Provided a general architecture overview. - Created guides for task closure and ChatGPT-Codex workflow. - Organized chat management guidelines for development projects. - Added template for current work status reporting.
65 lines
898 B
Markdown
65 lines
898 B
Markdown
# Arquitectura backend
|
|
|
|
## Objetivo
|
|
|
|
Definir la estructura, responsabilidades y reglas principales del backend.
|
|
|
|
## Organización
|
|
|
|
[Capas, módulos, bounded contexts o estructura principal.]
|
|
|
|
## Flujo de entrada
|
|
|
|
[Request → aplicación → dominio → persistencia → respuesta.]
|
|
|
|
## Responsabilidades
|
|
|
|
### Entrada / API
|
|
|
|
[Responsabilidades.]
|
|
|
|
### Aplicación
|
|
|
|
[Responsabilidades.]
|
|
|
|
### Dominio
|
|
|
|
[Responsabilidades.]
|
|
|
|
### Infraestructura
|
|
|
|
[Responsabilidades.]
|
|
|
|
## Casos de uso
|
|
|
|
[Convenciones y responsabilidades.]
|
|
|
|
## Servicios
|
|
|
|
[Convenciones y responsabilidades.]
|
|
|
|
## Repositorios
|
|
|
|
[Reglas y límites.]
|
|
|
|
## Persistencia
|
|
|
|
[ORM, mappers, modelos, transacciones.]
|
|
|
|
## Errores
|
|
|
|
[Estrategia de errores y mapeo.]
|
|
|
|
## Transacciones
|
|
|
|
[Reglas de atomicidad y rollback.]
|
|
|
|
## Seguridad
|
|
|
|
[Autenticación, autorización, tenancy, validación.]
|
|
|
|
## Referencias
|
|
|
|
- [ADR relacionado]
|
|
- [Documento relacionado]
|