Engineering & Architecture: Build Decisions This Week
2026‑09‑04
The past week’s headlines highlight a clear tri‑ad of priorities for engineering leaders across South Africa, the UK and the broader EU: vertical integration of critical stacks, AI–hardware co‑design, and agri‑finance ecosystems that demand on‑prem compliance. Each trend forces a distinct build‑or‑buy reassessment.
---
Nvidia’s $12.9 bn purchase of Hugging Face (Nvidia to buy developer platform Hugging Face in $12.9bn deal—The Guardian) signals that AI model deployment will increasingly happen on purpose‑built hardware rather than generic cloud APIs. The acquisition gives Nvidia a direct channel to the open‑source community that powers most industry‑grade LLMs, while simultaneously positioning its GPU portfolio at the centre of every new model run.
Build?
Pros: Full control over data residency – critical for POPIA (SA) and UK GDPR compliance; low latency for real‑time services such as fraud alerts or medical device telemetry; tighter security by keeping models in a hardened enclave.
Cons: Significant CAPEX on GPU clusters, need for dedicated ML ops staff, and higher energy bills that may be non‑trivial in regions with unreliable grids.
Buy?
Pros: Pay‑as‑you‑go from cloud providers, instant scalability across SA/EU, managed security updates.
Cons: Vendor lock‑in, limited visibility into model internals (a risk when data is sensitive), and higher cumulative cost if usage spikes.
Action point 1: Pilot a small micro‑service that runs a Hugging Face inference engine on an Nvidia RTX‑A6000 node in Johannesburg, benchmark throughput versus a cloud API, and quantify the regulatory impact of local hosting.
---
Doctors Without Borders is leveraging 3D printing to create prostheses and compression masks on site (How Doctors Without Borders uses 3D printing to help critical patients—MyBroadband). Their success hinges not only on the printers but also on robust, low‑latency control software that can ingest medical imaging, optimise slicer parameters and validate safety margins—all under bandwidth constraints typical of field environments.
Build?
Pros: Customisable workflow to match local regulatory standards (e.g., South African Medical Devices Act), offline operation in low‑connectivity zones, and the ability to integrate with mobile health records.
Cons: Requires a niche developer team with both software and biomedical expertise; ongoing maintenance of firmware across diverse printer models.
Buy?
Pros: Off‑the‑shelf SaaS solutions can reduce upfront engineering effort, often include certification pipelines.
Cons: Dependence on external networks for real‑time adjustments, limited auditability of data paths, potential export‑control restrictions when shipping hardware to conflict zones.
Action point 2: Build a containerised “Print‑Assist” stack (Python + Flask + Docker) that can run on an ARM‑based single‑board computer inside the printer enclosure. Validate offline operation for at least 48 hours and document compliance with POPIA for any patient data logged locally.
---
Discovery Group’s announcement of its first full‑year profit of R370 million as it gears up an October launch of a “super bank” (Adrian Gore sets an October date for Discovery's ‘super bank’—TechCentral) underscores how insurance and banking services are converging. The architectural implications are twofold: micro‑service boundaries between underwriting, payments, and AI‑driven advisory must be tightened, and data orchestration must satisfy both POPIA and the EU AI Act.
Build?
Pros: End‑to‑end ownership of sensitive financial data, ability to embed AI risk models in the same stack, easier audit trail creation for regulatory reviews.
Cons: Higher build effort across multiple domains (payments, KYC, fraud detection), potential duplication of services already offered by fintech incumbents.
Buy?
Pros: Pay‑for‑service APIs for payments, identity verification, and compliance; faster time‑to‑market.
Cons: Vendor lock‑in on core banking flows, limited flexibility to adjust risk thresholds or data retention policies without vendor cooperation.
Action point 3: Adopt a domain‑driven design where the “Risk Engine” micro‑service runs locally (on-prem in SA) and uses the Nvidia‑Hugging Face stack for real‑time scoring. Integrate with Discovery’s existing PostgreSQL data layer via an async event bus, ensuring all state changes are recorded in a GDPR‑compliant log.
---
---
The convergence of deep‑learning on purpose‑built GPUs, the need for offline medical manufacturing support, and the rise of insurance‑bank hybrids present three concrete build decisions that can deliver tangible ROI in the next 12–18 months. Prioritise local hosting where regulatory or performance constraints demand it; otherwise, lean on managed services to accelerate innovation.
---
Sources