How rohanpatel981/consolidation-pipeline-design works
This repository is an architecture write-up for a multi-tenant financial consolidation system, not the system’s source code. The documented user workflow is direct browser upload to S3, followed by asynchronous file processing, consolidation, and status or business operations through the platform service. The pipeline stages and major accounting capabilities are represented from the README; detailed implementation calls cannot be verified from source excerpts.
Main entry points: architecture.md File processing · pipeline.md Final consolidation · 0001-sax-streaming-over-dom.md Streaming extraction
Components 17
Client
- Browser UI
Backend services
- Shared core
docs/architecture.md - Platform service
docs/architecture.md - File processing
docs/architecture.md
Consolidation pipeline
- Trial-balance upload
docs/scaling.md - Streaming extraction
docs/adr/0001-sax-streaming-over-dom.md - Pre-consolidation data
docs/pipeline.md - Nine-module processing
docs/pipeline.md - Retained earnings
docs/pipeline.md - Currency translation
docs/pipeline.md - Final consolidation
docs/pipeline.md - Accounting operations
docs/architecture.md
Infrastructure
- AWS S3
- MongoDB
- MySQL
- Redis
- RabbitMQ
Connections 23
- Browser UI → AWS S3: uploads directly
- Browser UI → Platform service: uses REST
- Platform service → Shared core: depends on
- File processing → Shared core: depends on
- Platform service → File processing: dispatches via RabbitMQ
- File processing → AWS S3: reads files
- File processing → Streaming extraction: streams rows
- Streaming extraction → Pre-consolidation data: produces data
- Pre-consolidation data → Nine-module processing: feeds processing
- Nine-module processing → Redis: increments counters
- Redis → File processing: coordinates watcher
- File processing → Retained earnings: starts after coordination
- File processing → Currency translation: starts after coordination
- Retained earnings → Final consolidation: contributes to
- Currency translation → Final consolidation: contributes to
- Platform service → MongoDB: reads and writes
- Platform service → MySQL: reads and writes
- Platform service → Redis: uses counters and locks
- Platform service → RabbitMQ: publishes and consumes
- File processing → MongoDB: reads and writes
- File processing → RabbitMQ: publishes and consumes
- Final consolidation → MongoDB: stores consolidation data
- Accounting operations → Platform service: managed through