The cloud as seen from Yaoundé, not from a brochure
The reference architectures of the big cloud providers are written for companies with redundant fibre and no data-residency constraints. That is not the context of most of our clients. In the CEMAC region, the right architecture works with real-world connectivity, the sovereignty requirements of public institutions and a foreign-currency budget that must be defended — which often means a hybrid: an on-premise footprint in Cameroon, interconnected with AWS or Azure through VPN or a dedicated link, with genuinely elastic workloads on the cloud side.
We refuse two shortcuts. Wholesale lift-and-shift, which relocates your problems and adds a monthly invoice. And dogmatic cloud-first, which ignores that a production application can have excellent reasons to stay on site. Every application gets a cloud-readiness score, every choice is documented, and the architecture is reviewed against the Well-Architected Framework before anything moves. It is the same rigour we apply to the ERP rollouts that later run on these infrastructures.
Technical stack
- Cloud: AWS (EC2, ECS, EKS, RDS, S3, Lambda, CloudFront), Azure (App Service, AKS, Functions, SQL Database)
- IaC: Terraform, AWS CloudFormation, Azure Bicep
- CI/CD: GitHub Actions, Azure DevOps, GitLab CI
- Containers: Docker, Kubernetes (managed or self-hosted)
- Observability: Prometheus, Grafana, Datadog, CloudWatch, Application Insights