Enterprise Architecture for African Scale

Start with constraints, not catalogues

Enterprise platforms fail quietly when architecture is treated as decoration. Useful architecture begins with constraints: regulatory expectations, connectivity realities, organisational capacity, and the cost of downtime.

Across African operating environments, those constraints are not edge cases. Intermittent connectivity, multi-currency settlement, and institutions that grow faster than their documentation are the default.

Model the domain before choosing frameworks.

Boundaries that match the organisation

Draw service boundaries around business capabilities that change at different speeds. Finance reconciliation and citizen status tracking should not share a deploy unit simply because both are “backend.”

When org charts shift, modular boundaries absorb the change. Monoliths without seams force rewrites disguised as migrations.

Design for offline as a first-class path

Offline is not a mobile convenience feature when clinics, field officers, or branch staff depend on the system. Sync contracts, conflict rules, and idempotent writes belong in the architecture review—not the backlog.

type SyncBatch = {
  deviceId: string;
  since: string;
  mutations: Mutation[];
};

// Reject silent loss: every accepted mutation gets an ack + audit id.

Operability is part of the product

Instrument early so performance regressions are visible. Document decisions so the system survives team change. Treat security and accessibility as launch blockers—not optional polish.

If you are evaluating a build partner, ask how they handle maintenance, observability, and knowledge transfer—not only how the first release looks.