Current system architecture
A code-level view of the current UAT architecture and how the application, data stores, workers and Go services fit together.
Go services: responsibilities and fallbacks
What each Go service does, which product uses it, and what happens when it is unavailable.
Mobile sync: end-to-end data flow
How a field device moves assignments and offline transactions through the current Go sync architecture safely.
TALA Flow runtime and collection paths
How form design, XLSForm processing, public collection, OpenRosa clients, submissions and exports move through the platform.
Dashboard, outbox and snapshot architecture
How OneTALA keeps operational writes authoritative while building faster campaign decision views.
High-volume import architecture
How large geography, user, stock and beneficiary imports are admitted, claimed, processed and monitored.
Large report and export architecture
How Campaigns, Workforce and Flow export large datasets without exhausting PHP memory.
Large XLSForm processing architecture
How TALA Flow handles large choice sheets without loading the complete workbook into PHP memory.
Service health and observability
What to monitor across Laravel, PostgreSQL, Redis, queues and the Go worker services.
Deployment profiles and scaling model
When to use the current small-VPS profile, the full-scale overlay, or managed cloud services.