#Deployment
Deployment engineering ensures that systems move from development to production reliably. Articles cover Cloud Run deployment for multi-agent services, A2A endpoint exposure, embed.FS for single-binary Go deployments, and the strategies that make deployments repeatable and rollback-safe.
5 posts tagged with deployment. ← All posts
How you put new code into production is a design decision with real consequences for risk and downtime. Deploy it all at once and a bad release hits everyone; roll it out gradually and you can catch problems while they're small. Blue-green, canary, rolling, and feature flags are the core techniques — each trading complexity for safety in a different way. This post covers when and why to use each.
How you put new code into production is a design decision with real consequences for risk and downtime. Deploy it all at once and a bad release hits everyone; roll it out gradually and you catch problems while they're small. Blue-green, canary, rolling, and feature flags are the core techniques — each trading complexity for safety differently. When and why to use each.
The demo ran on your laptop with clean data — production means the customer's messy systems, their security rules, and their data as it actually is, which is where most forward deployed work is really won.
Production means the customer's messy data, systems you don't control, and security you must pass: profiling dirty data, loose-coupling integrations, treating security/residency as gates, and deploying + handing over so you can actually leave.
Building a computer-vision system that works in a demo is one thing; building one that works reliably in the real world — at the right speed, cost, and robustness — is another. This closing post assembles the series into practical judgment: how to approach a vision problem, the deployment realities that trip teams up, and where the field is heading. It turns pixels-to-understanding from a concept into something you can actually ship.
Building a vision demo is one thing; shipping a reliable system at the right speed, cost, and robustness is another. A workflow for approaching a vision problem, the deployment realities (efficiency for real-time/edge, robustness to distribution shift, edge cases, monitoring), and where the field is heading — multimodal and foundation models.
Running agents on Cloud Run, exposing via A2A, and wiring into production systems.
Deploy Microsoft Agent Framework multi-agent systems on Cloud Run with A2A agent-to-agent communication, autoscaling, load balancing, and production observability dashboards.
Go's embed.FS bundles files into the binary at compile time. The pattern collapses what would be a multi-artefact deploy into one binary. Three places it pays back daily.
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.