Two days out. The Google Cloud Run Hackathon is this Wednesday, October 14, and submissions close at midnight PT tomorrow.
The mechanics, one more time: - Deploy and run your product on Google Cloud Run that's what makes you eligible - Schedule your launch for Wednesday, October 14 - Get it in before midnight PT tomorrow
Every eligible launch picks up $50 in Google Cloud credits. Winners take $500 in credits, a spotlight on Google Cloud's own channels, and a 1:1 with the Cloud Run team.
I've been thinking about the trade-off with serverless platforms like Cloud Run.
Scaling to zero sounds ideal for a small product: no traffic, no compute running. But real apps aren't always just HTTP requests. You have scheduled jobs, background tasks, webhooks, database connections, and work that shouldn't disappear halfway through execution.
How do you structure a real production app around scale-to-zero? Do you keep everything serverless, split workloads between services and jobs, or eventually move to something always running?
I'd be especially interested in hearing what worked (or surprised you) in an actual project.
Google Cloud Text-to-Speech enables developers to synthesize natural-sounding speech with 30 voices, available in multiple languages and variants. It applies DeepMind’s groundbreaking research in WaveNet and Google’s powerful neural networks to deliver the highest fidelity possible.
Cloud Composer, by Google is a fully managed workflow orchestration service that empowers you to author, schedule, and monitor pipelines that span across clouds and on-premises data centers.
