Gocloud — designing a unified API library for AWS, GCP,...
What it actually takes to build a unified cloud API library — and why "write once, run anywhere" still doesn't quite work, even for the patterns where it almost does.
#Multi-Cloud
Multi-cloud architecture distributes workloads across multiple cloud providers for resilience, cost optimisation, or regulatory compliance. Articles cover Gocloud's provider-agnostic API, egress cost reduction, and the engineering patterns for running systems that span AWS, GCP, and Azure.
2 posts tagged with multi-cloud. ← All posts
Egress costs — the gotcha that kills cloud-arbitrage plans
Cross-cloud data movement is billed by the GB. The bill is invisible until it isn't. A multi-region or multi-cloud architecture that doesn't model egress costs in design will discover them in production.
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.