Engineering & Architecture: Build Decisions This Week
2026‑09‑23
The week’s headlines underline three concrete levers that can shape the technology stack of a South African or UK/EU‑based company in 2026: (1) agentic AI for orchestration, (2) the stark bandwidth divide between public and private schools, and (3) the urgency of real‑time analytics for safety dashboards. Each decision carries trade‑offs that should be quantified before any production roll‑out.
---
“How agentic AI is transforming South African security operations” in TechCentral documents how SA’s SOCs are moving from manual playbooks to token‑driven workflows that let a single LLM call sub‑agents, preserve state and invoke external APIs. The same architecture can power internal bots such as PR commentary or code‑review assistants.
Pros
| Benefit | Rationale |
|---------|-----------|
| Rapid prototyping | A new bot can be spun up in minutes rather than weeks of coding a micro‑service. |
| Unified observability | Every token exchange is logged, giving a single trace for end‑to‑end debugging. |
| Operational simplification | One entry point removes the need to manage multiple service instances. |
Cons
| Risk | Mitigation |
|------|------------|
| Compute cost scales with token usage | Budget guardrails; switch to model pruning or smaller LMs for non‑critical paths. |
| PII leakage if tokens contain sensitive data | Sanitize logs; enforce zero‑knowledge policy; encrypt transient state. |
| Latency from repeated external API calls | Cache results; batch requests; consider hybrid local micro‑services for latency‑sensitive tasks. |
Build Decision #1 – Pilot a low‑risk agentic bot in the CI/CD pipeline
Start with an automated PR commentary bot that uses the same LLM orchestration pattern described in TechCentral’s article. Measure token volume, cost per PR, and reviewer satisfaction. This will provide concrete data on whether the benefits outweigh the operational overhead before committing to broader adoption.
---
“MyBroadband” reports that public schools in South Africa receive only 10 Mbps while private providers deliver up to 1 Gbps. This divide forces product teams to adopt dual‑tier architectures: feature‑rich experiences for high‑bandwidth users and lightweight, progressive interfaces for low‑bandwidth environments.
Trade‑offs
| Choice | Advantage | Disadvantage |
|--------|-----------|--------------|
| CDN + adaptive image/video compression | Faster load times everywhere; reduced server cost | Requires extra tooling; may degrade quality on 1 Gbps links if not tuned. |
| Edge computing (serverless functions at ISP edges) | Near‑real‑time processing; less round‑trip latency | Cold start penalties for sporadic traffic; vendor lock‑in risk. |
| Offline caching + data sync (PWA) | Works offline; minimal bandwidth use | Complexity in conflict resolution; limited real‑time features. |
Build Decision #2 – Deploy a tiered front‑end with progressive enhancement
Implement a single SPA that detects connection speed and serves compressed assets or reduced feature sets accordingly. Use modern build tools to generate two bundles: a “lite” bundle for ≤10 Mbps connections and a “full” bundle for higher speeds. This mitigates the user experience gap highlighted by MyBroadband without a costly rewrite of backend services.
---
The digital dashboard described in MyBroadband’s article on road incidents gives Limpopo’s government instant visibility into crashes, speeding and taxi patterns. Delivering actionable insights requires streaming ingestion, low‑latency processing, and secure data handling.
Architecture options
| Stack | Strength | Weakness |
|-------|----------|----------|
| Kafka + Flink (or Spark Structured Streaming) | Proven latency < 1s; fault‑tolerant | Operational overhead; requires dedicated cluster. |
| Serverless event streaming (e.g., AWS Lambda + Kinesis) | Pay‑per‑use; scales automatically | Cold start can add 100‑200 ms; stateful ops harder to manage. |
| On‑prem microservice with in‑memory data store (Redis Streams) | Full control over data residency | Higher CAPEX; requires dedicated infra. |
Build Decision #3 – Adopt a hybrid serverless‑streaming pipeline
Use Kinesis for ingestion, Lambda for lightweight transformation, and Redis Streams as a short‑term state store before persisting to PostgreSQL. This balances cost (pay‑per‑invoke) with the need for sub‑second latency in safety alerts, while keeping data residency compliant with POPIA/UK GDPR via on‑prem encryption at rest.
---
---
The cost model for token‑based agentic orchestration assumes a linear relationship between tokens and compute. Validate the pricing tiers of the chosen LLM provider (OpenAI, Anthropic) against actual usage patterns in your pilot. Edge‑compute recommendations rely on the assumption that ISP edge locations are available in all target regions; confirm availability with local cloud providers.
---
Sources