Split-Cloud Transaction Architecture
Measure the consequences of running application compute outside Nigeria while maintaining transaction data on Nigerian infrastructure.
- AUTHOR
- Hexcore Engineering Lab
- UPDATED
- 2026-10-04
- EVIDENCE STATE
- HYPOTHESISED / PLANNED
01 / Research question
What latency, throughput and operational costs emerge when transaction compute and persistent data are geographically separated?
Hypothesis — not a finding
Chatty request paths will amplify network round-trip time, increasing tail latency and reducing effective connection capacity.
02 / Architecture
Foreign public cloud
Payment API
Application compute
Secure connectivity
Encrypted link
Cross-border path
Nigerian infrastructure
PostgreSQL
Transaction data
03 / Environment
- Compute location
- Foreign public cloud — to be selected
- Data location
- Nigerian-hosted infrastructure
- Connectivity
- Encrypted cross-border network path
- Data
- Synthetic only; no customer or production data
04 / Methodology
A planned synthetic transaction API with controlled database round trips and connection-pool settings.
- 01Establish a co-located baseline
- 02Hold workload and schema constant
- 03Move application compute across the network boundary
- 04Measure at increasing concurrency
- 05Vary application round-trip count
- 06Repeat and compare distributions
05 / Measurements
Network RTT
Database round trips
Transaction latency
Throughput
Jitter
Connection pool behaviour
Cross-border traffic
Cost
06 / Results & observations
This experiment has not yet been executed.
This space will contain measured results, observations and failure modes after repeated runs and methodological review. No benchmark values are available yet.
07 / Limitations
- —Provider and region selection are pending
- —Internet paths can vary by time and carrier
- —Architecture alone does not establish regulatory compliance
08 / Reproduction & artefacts
Commands, configuration, dataset generators and raw data will be linked here when they exist.
Related experiments
Conceptual topology
Baseline pending
Resilience
Cross-Border Failure Simulation
Understand how a split-cloud financial workload behaves when connectivity between foreign compute and Nigerian infrastructure is degraded or unavailable.
Conceptual topology
Baseline pending
Data localisation
Workload Localisation Patterns
Compare placement strategies for transaction-critical services, persistent data and supporting workloads.