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.
47 lines
707 B
Markdown
47 lines
707 B
Markdown
# Arquitectura de datos y persistencia
|
|
|
|
## Objetivo
|
|
|
|
Definir las reglas de persistencia, integridad y evolución de datos.
|
|
|
|
## Base de datos
|
|
|
|
[Motor, versión y configuración relevante.]
|
|
|
|
## Modelado
|
|
|
|
[Convenciones para tablas, columnas, claves y relaciones.]
|
|
|
|
## Persistencia
|
|
|
|
[ORM, repositorios y mappers.]
|
|
|
|
## Transacciones
|
|
|
|
[Reglas de atomicidad.]
|
|
|
|
## Integridad
|
|
|
|
[Constraints, foreign keys, invariantes críticas.]
|
|
|
|
## Concurrencia
|
|
|
|
[Locks, versionado, idempotencia, etc.]
|
|
|
|
## Migraciones
|
|
|
|
[Estrategia de migraciones.]
|
|
|
|
## Índices y rendimiento
|
|
|
|
[Convenciones y criterios.]
|
|
|
|
## Datos legacy
|
|
|
|
[Reglas para compatibilidad y eliminación.]
|
|
|
|
## Referencias
|
|
|
|
- [ADR relacionado]
|
|
- [Documento relacionado]
|