How ana2320-ux/sistema_distribuido_srb works
SRB is a three-tier ticket-reservation system: clients query events, reserve or modify seats synchronously, and cancel asynchronously. The synchronous route passes through the Transaction Manager, RMC business logic, persistence client and persistence service to SQLite; cancellations are acknowledged first, then processed and reported by notification. The README also documents read scaling, retries and idempotent writes. Some cancellation internals and deployment behavior are described only in the README; the graph does not infer unsampled call details.
Main entry points: cliente.py Client API · gestor_transacciones.py Transaction Manager · cliente_persistencia.py Persistence client · main.py Cancellation service
Components 16
Client layer
- Client API
capa_cliente/cliente.py - Operation scripts
capa_cliente/script.py - Load scenarios
capa_cliente/carga.py - Locust driver
capa_cliente/locustfile.py
Business layer
- Transaction Manager
capa_negocios/gestor_transacciones.py - RMC service
capa_negocios/rmc.py - Cancellation service
capa_negocios/main.py - Persistence client
capa_negocios/cliente_persistencia.py - Transaction metrics
capa_negocios/metricas.py
Persistence layer
- Persistence service
capa_persistencia/servicio_persistencia.py - SQLite database
capa_persistencia/db.py - Read replica
capa_persistencia/main.py - Catalog loader
capa_persistencia/cargar_datos.py
Protocol and telemetry
- JSON message protocol
config/E_mensaje.py - Runtime configuration
config/configuracion.py
Other components
- Reservation client
Connections 23
- Reservation client → Client API: submits operations
README.md - Client API → Transaction Manager: sends requests
README.md - Client API → Cancellation service: receives notification
README.md - Operation scripts → Client API: executes operations
capa_cliente/main.py - Locust driver → Load scenarios: generates load
capa_cliente/locustfile.py - Load scenarios → Client API: sends requests
capa_cliente/carga.py - Transaction Manager → RMC service: dispatches requests
README.md - RMC service → Persistence client: requests persistence
capa_negocios/rmc.py - Persistence client → Persistence service: sends requests
capa_negocios/cliente_persistencia.py - Persistence service → SQLite database: reads and writes
capa_persistencia/servicio_persistencia.py - Transaction Manager → Cancellation service: queues cancellation
README.md - Cancellation service → Persistence service: releases reservation
README.md - Cancellation service → Client API: sends result
README.md - Persistence client → Read replica: routes reads
README.md - Read replica → SQLite database: reads shared store
README.md - Catalog loader → SQLite database: loads catalog
capa_persistencia/cargar_datos.py - Transaction Manager → Transaction metrics: records measurements
capa_negocios/gestor_transacciones.py - Client API → JSON message protocol: encodes messages
capa_cliente/cliente.py - Transaction Manager → JSON message protocol: decodes messages
capa_negocios/gestor_transacciones.py - RMC service → JSON message protocol: builds requests
capa_negocios/rmc.py - Persistence service → JSON message protocol: builds responses
capa_persistencia/servicio_persistencia.py - Client API → Runtime configuration: reads endpoints
capa_cliente/cliente.py - Persistence client → Runtime configuration: reads endpoints
capa_negocios/cliente_persistencia.py