Engineering & Architecture: Build Decisions This Week
2026‑09‑20
---
The tech landscape is still being reshaped by two very different forces this week: the relentless march of AI‑driven delivery pipelines and the hard‑line reality that operational risk, even in seemingly unrelated sectors like airlines, keeps pushing for architectural resilience. Below are the most actionable takeaways for any CTO navigating South African and UK/EU ecosystems.
---
OpenAI’s latest exposition of its agentic software factory exposes a production model that treats the LLM as an orchestrator rather than a single‑purpose inference engine. The architecture moves from batch micro‑services to a continuously‑running, token‑driven loop capable of invoking external tools, maintaining state and spawning sub‑agents.
| Benefit | Trade‑off |
|---------|-----------|
| Rapid prototyping of internal bots (e.g., PR reviewers, code linting) | Persistent compute cost per token; higher latency for large models |
| Centralised logging via the factory’s tracing | Potential leakage of PII if tokens are not scrubbed before storage or transmission |
| Simplified CI‑pipeline integration – a single entry point triggers all downstream tool calls | Requires tight outbound‑traffic controls to satisfy data‑protection regimes |
For teams that have already hit the “build‑once, run everywhere” wall, this model is tempting. However, the cost of an unlimited token budget is non‑trivial in 2026, especially when PII handling rules in SA (POPIA) and EU (GDPR + AI Act) demand strict observability and auditability.
Build Decision #1 – Should your product teams adopt an agentic factory pattern for internal tooling?
We recommend piloting the model on a single non‑critical service, measuring token usage per hour against the projected cost of equivalent dedicated micro‑services. If the ROI in developer velocity exceeds 30 % and no PII leaks are detected in audit logs, scale incrementally.
---
Capitec Connect and FNB Connect are running “the same MVNO playbook” yet diverge only by the core banking institution they partner with. The key takeaway is that the infrastructure is commodified—value lies in proprietary data‑integration layers, not raw connectivity.
For fintechs contemplating a mobile network to deliver banking services directly to end‑users, this suggests:
Build Decision #2 – Should you integrate a telco‑as‑a‑service layer into your product?
Start by mapping out the required QoS parameters against your SLAs. If latency targets exceed what any telco can guarantee, you might need an on‑prem edge cache or a hybrid model that balances public and private networks.
---
The “Migrations at Scale: Changing the Application Engine at 30,000 Feet” article outlines a disciplined approach to swapping database engines without service interruption. The pattern relies on:
For an e‑commerce platform or any mission‑critical ordering system, this approach can reduce maintenance windows from days to minutes.
Build Decision #3 – Do you need a zero‑downtime migration strategy?
If your current database is approaching its horizontal scalability limits—order histories are loading slowly and engineers spend 4× more time on maintenance—implement the dual‑write pattern. Monitor latency metrics at the API gateway; if the new store’s read performance improves by >40 % within the first week, consider promoting it fully.
---
The agentic factory model highlights a vulnerability that is often overlooked: tokens may contain PII or sensitive credentials. Coupled with the airline strike story (easyJet cabin crew plan strikes) which underscores how quickly service disruptions can cascade, security governance becomes paramount.
---
---
I have highlighted three concrete build decisions that align with the sources provided, but specific platform choices (e.g., AWS vs GCP for the agentic factory) and cost estimates rely on assumptions about token pricing and data‑transfer volumes. These will need validation against your current spend sheets and vendor quotes.
---
Sources