BACKEND ARCHITECTURE
JUNGLEWORKS
Dispatch platform engineering
Service segmentation, data integrity and resilience work across the Tookan ecosystem for enterprise clients in Saudi Arabia and the UAE.
- Node.js
- MySQL
- MongoDB
- Redis
- API response time
- 61.3%
- Incident response
- 89%
- Daily deliveries
- 14K+
API response time
Incident response
Daily deliveries
The constraint
A configurable dispatch platform is not one product — it is one codebase asked to be a different product for every client. The work is deciding what stays shared, what gets segmented into its own service, and where a client-specific rule is allowed to reach.
Production backend
REQUEST PATH
Dispatcher consoles and operations dashboards, Angular through v18 as microfrontends.
- CONFIGURABLE BUSINESS LOGIC
- Client requirements translated into dispatch configurations, technical specs, validation criteria and production-ready workflows for NEOM, Red Sea Global and DUBZ.
- DATA INTEGRITY
- Replication and read replicas across MySQL, MongoDB and Redis, with production migrations and schema updates run at near-zero downtime.
- FAILURE-POINT ANALYSIS
- Automated monitoring and alerting pipelines built around where the platform actually breaks, not where it is easiest to instrument.
- FRONTEND MODERNISATION
- Angular v5 to v18 restructured into scalable microfrontends — operational efficiency up 45%, data accessibility up 60%.