Consistent Hashing in Go: Why hash(key) % N Breaks and How a Ring Fixes It

Add one server to a cache cluster that uses hash(key) % N and about 91% of your keys change owner overnight. Consistent hashing cuts that to roughly K/N. We build the ring in Go, add virtual nodes, and measure real remapping and load balance, including the hash function mistake that quietly wrecks it.

Every Prompt Is a Cross-Border Transfer: AI Governance Under Law 2019-014

A company in Lomé or Dakar wires two hundred employees to American inference APIs, and nobody files anything. This article argues that a prompt containing customer data is a transfer of personal data to a third country in the sense of Togo's law 2019-014, that an LLM gateway does not change the legal nature of that transfer but is what makes it declarable, and that the residency options available to a West African company rank very differently on paper than they do once GPU prices, currency exposure and payment friction are counted.

Giving Your Teams a Real AI Budget with LiteLLM

A hands-on guide to putting a gateway between your people and the model vendors, so that every call is attributed to a named person and a team, every team has a ceiling that resets on a schedule, a daily bound contains the runaway agent, and the finance team finally gets a per team breakdown. Covers deployment with Docker and Postgres, teams and keys, stacked budget windows, rate limits, model tiering, request tags for chargeback, PII guardrails, and the day two work nobody warns you about.

Nobody Knows What Your Company Spends on AI

Every company now has employees using OpenAI, Anthropic and Gemini every day, and almost none of them can say who asked what, what data left the building, or what any of it returned. This article argues that AI governance by policy fails for the same reason shadow IT policies failed, that the request for a fixed AI budget is the wrong question, and that FinOps is the practical way in: the only one of the three unknowns you can measure today is cost, and measuring it is what buys you the other two.

A Reference Architecture for a Sovereign Government Cloud

The two previous articles showed where Togolese law and Kubernetes fail to meet, then why multi-cloud does not answer a jurisdictional question. This one proposes what to build: a reference architecture for a sovereign government cloud in the WAEMU context. Requirements derived from the legal texts, layer-by-layer design choices with their justifications, an operating model, stated limits, and an honest comparison with the alternatives. An architecture document, not a tutorial.

The Multi-Cloud Illusion for the State: Duplication Is Not Sovereignty

Multi-cloud is sold to African countries as the answer to both resilience and digital sovereignty: spread workloads across several hyperscalers and you dilute risk and vendor power. Under Togo's Law 2019-014 on personal data and the ANCY cybersecurity regime, that promise does not hold. This article argues that multi-cloud does not divide legal exposure, it multiplies it, and closes with a decision framework for when it is legitimate and when it is not.