Area—01✦
Data localisation
Trace where regulated data moves, rests, and leaves an operational footprint.
Planned · measured · reproducible
Engineering systems,
under real-world constraints.
We build, benchmark and break real systems to understand how they behave under production conditions.
3 system boundaries
evidence state: planned
evidence state: planned
latency · resilience
throughput · failure
λ∑throughput · failure
data localisationcloud infrastructuredistributed systemsdatabasesresiliencecybersecurityperformance engineeringdata localisationcloud infrastructuredistributed systemsdatabasesresiliencecybersecurityperformance engineering
01—Current research
Questions grounded in systems, not slogans.
Operational questions for teams building and running critical infrastructure in Nigeria.
Area—02✦
Cloud infrastructure
Evaluate infrastructure through realistic application and database workloads.
Area—03✦
Distributed systems
Study latency, consistency and failure across geographic system boundaries.
Area—04✦
Databases
Benchmark transaction performance, topology, backup and recovery behaviour.
Area—05✦
Cybersecurity
Test security properties, controls and failure boundaries under pressure.
Area—06✦
Performance engineering
Measure distributions and bottlenecks instead of relying on assumptions.
02—Experiment register
Planned work, made explicit.
Every study carries a question, evidence state, methodology and reproduction path.
EXP-001PLANNED
Conceptual topology
Baseline pending
Databases
PostgreSQL on Nigerian Cloud Infrastructure
Establish a baseline for PostgreSQL performance and operational characteristics on Nigerian-hosted cloud infrastructure.
EXP-002PLANNED
Conceptual topology
Baseline pending
Data localisation
Split-Cloud Transaction Architecture
Measure the consequences of running application compute outside Nigeria while maintaining transaction data on Nigerian infrastructure.
EXP-003PLANNED
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.
EXP-004PLANNED
Conceptual topology
Baseline pending
Data localisation
Workload Localisation Patterns
Compare placement strategies for transaction-critical services, persistent data and supporting workloads.
03—Method
Measure, don’t assume.
A repeatable path from research question to documented evidence.
Protocol / v0.1
Define the environment. Isolate the variable. Stress the boundary. Publish the evidence.
Read the methodology →01
Define
Question, environment, workload
02
Measure
Baseline and controlled variable
03
Stress
Failure, recovery, repetition
04
Publish
Evidence, limitations, reproduction
Applied engineering
Working on data localisation or cloud repatriation?
Hexcore helps organisations map workloads and data flows, design target environments, execute migrations and validate production readiness.