Building the Foundation of a Cloud-Native Survey Engine

2026 · Biami: An Autonomous Cloud-Native Survey Engine

Biami (Ewe: "Ask Me") is an autonomous, production-grade survey platform engineered for high-concurrency data ingestion. This phase of the project established the architectural bedrock and the core API layer required to handle complex, multi-channel communication (USSD, SMS, and PWA) at scale.

The Vision

The primary goal was to design a system capable of bridging the gap between sophisticated data collection and accessibility in under-served regions. By focusing on a decoupled, event-driven architecture, Biami is built to be resilient, cost-effective, and horizontally scalable.

Core Achievements

• Engineered the "Data Core": Defined a dynamic JSON schema for survey questions and respondent metadata, allowing the platform to ingest unstructured data without requiring frequent database migrations.
• High-Performance API Implementation: Developed the initial API layer using Golang and the Gin framework. This choice was strategic, prioritizing Go’s superior concurrency model for handling thousands of simultaneous USSD session webhooks.
• Production-Ready Containerization: Implemented a multi-stage Docker build process to ensure a minimal attack surface and optimized deployment footprints for cloud environments.
• Professional Project Orchestration: Established a standard Go project layout (following the cmd/internal/pkg pattern) and a centralized Makefile for automated testing and builds.

Technical Implementation

The architecture centers on a high-speed webhook handler designed to interface with global mobile gateways.

• Language: Golang 1.22
• Framework: Gin Gonic
• Deployment: Docker (Containerized Microservice)
• Pattern: Monorepo with a separation of concerns between business logic (/internal) and public entry points (/cmd).

Architectural Decisions & Lessons Learned

Transitioning to a Cloud-Native Stack

While the initial blueprint for this project was based on Django, I made the executive architectural decision to pivot to Golang for the API layer. This shift ensures the project aligns with modern Infrastructure as Code (IaC) standards and provides the low-latency performance required for real-time USSD interactions.

Documentation as Code

I adopted an Architecture Decision Record (ADR) workflow early in the process. Documenting the "why" behind every tool choice—from the Gin framework to the multi-stage Docker build—proved essential for maintaining clarity and professional rigor as the system complexity grew.

The Power of Identity

Naming the project Biami ("Ask Me" in Ewe) served as a constant reminder of the user-centric mission. It reinforced the importance of designing for accessibility, ensuring that the underlying cloud infrastructure supports users on basic mobile devices just as effectively as those on modern PWAs.

Future Trajectory

With the core API and data schemas established, the project is positioned to move into full-scale cloud orchestration, utilizing Terraform for environment provisioning and serverless patterns for autonomous data processing.

*****

Key Competencies Demonstrated

Golang System Design Docker API Development Architectural Documentation Cloud-Native Patterns