Engineering & Architecture: Build Decisions This Week

Engineering & Architecture: Build Decisions This Week

2026‑09‑10

---

1️⃣ Platform Landscape – The Quiet Growth of Cloud Value

The South African Cloud Value Realisation Index 2026, highlighted by BusinessTech and MyBroadband, shows that organisations are still wrestling with extracting tangible ROI from cloud spend. No new provider features appeared this week, but the fact that the index is being compiled signals a broader industry need: measurable outcomes over shiny bells‑and‑whistles.

Build Decision #1 – tighten IaC hygiene and drift detection

• What to do: Allocate a sprint to audit existing Terraform modules (or the equivalent IaC tool your team uses) for drift, tag modules with version constraints, and embed drift‑check steps in CI pipelines.
• Trade‑off: A few extra hours now can prevent weeks of manual remediation or unforeseen cost spikes later. The alternative—relying on ad‑hoc provisioning logs—keeps the risk window open.

In South Africa, where bandwidth is improving but not uniformly reliable, consolidating cloud footprints also reduces network latency and data egress costs, a point the survey indirectly underscores by asking companies to evaluate “biggest obstacles” to value realization.

---

2️⃣ Architecture Patterns – Concurrency & Isolation

American Express’s payment processing case study, published in ByteByteGo’s September 2026 newsletter, shines light on two classic pitfalls of high‑volume transactional services: fragile authentication flows and brittle error handling. The post highlights how the company leverages WorkOS Emulate to run the WorkOS API locally for development and automated testing, thereby exposing failures that would otherwise surface only in production.

Key takeaways:

• Isolate auth from core logic – keep the token‑validation layer separate so you can swap in a mock or emulator without touching business code.
• Test end‑to‑end flows early – include full SSO login cycles, signed webhooks, token refresh and error paths in unit/Integration suites before merging to prod.

Build Decision #2 – adopt local authentication emulation

• What to do: Integrate the WorkOS Emulate workflow (or a similar tool) into your CI pipeline so that every commit triggers a full auth flow test against a sandboxed API.
• Trade‑off: It adds latency to the pipeline and requires maintaining a mock spec, but it drastically reduces “works in staging, breaks in production” incidents.

---

3️⃣ Developer Tooling – From Groundwork to Edge

The MyBroadband story about Fibertime shows how a township fibre operator is using drones to plan the ground network for its massive rollout. The company has purchased a drone firm after spending “millions of rands” on aerial surveys and uses those data to orchestrate the physical deployment of 100 Mbps fibre to over 500,000 users, with a pipeline of one million homes.

What this implies for software teams:

• Integrate geospatial analytics into planning pipelines – ingest drone imagery, run automated edge‑selection algorithms and expose the results via an API for field teams.
• Embrace asynchronous task orchestration – flight data arrives in bursts; use message queues (Kafka/RabbitMQ) to decouple ingestion from downstream processing.

Build Decision #3 – embed drone‑derived geospatial data into network planning services

• What to do: Build a microservice that ingests the drone survey payload, runs clustering on potential fibre drop points, and exposes candidate routes via GraphQL.
• Trade‑off: Adds complexity in data handling (image processing pipelines) but unlocks near‑real‑time deployment optimization across disparate townships.

---

4️⃣ Security & Compliance – A Governance Lens

The Moneyweb article “Tongaat Hulett scandal: Thursday court appearance for former directors” reminds us that governance failures can ripple into the technical realm. Even if no new legislation appears this week, a robust audit trail and role‑based access controls (RBAC) are non‑negotiable.

• Audit trails: Ensure every IaC change is logged with author, timestamp, and reason.
• RBAC tightening: Limit who can trigger drone‑data pipelines or modify network plans.

---

Quick Takeaway Checklist

| Decision | Why it matters | Immediate action |

|----------|----------------|------------------|

| Tighten IaC hygiene | Avoid cost surprises & drift | Run Terraform plan dry‑runs in CI |

| Adopt auth emulation | Reduce prod‑failures | Add WorkOS Emulate step to nightly pipeline |

| Integrate drone data | Accelerate fibre rollout | Build geospatial microservice and expose GraphQL |

---

Review Note:

• The recommendation to use WorkOS Emulate assumes that the organisation’s authentication stack is compatible with WorkOS. Validate tooling fit for current auth providers (e.g., Okta, Auth0).
• Embedding drone data presupposes a stable API from the purchased drone firm; confirm versioning and SLAs before committing.
• IaC drift detection relies on Terraform – if the team uses Pulumi or CDK, equivalent drift checks must be mapped.

---