Why we migrated to Firebase and GCP: Smash.gg

Smash.gg, an esports platform supporting nearly 2,000 monthly events and more than 60,000 competitors, adopted Firebase in 2016 after an unreliable third-party chat service exposed the need for dependable real-time tournament interactions. Firebase Realtime Database synchronized match status between players, while a Firebase-based chat feature was built and productionized within days; Firebase Cloud Messaging and Cloud Functions later enabled browser notifications for events such as moderator requests. After evaluating Google Cloud Platform at Google Cloud Next 2017, the company migrated key systems to Container Engine, Kubernetes, Pub/Sub, Cloud SQL, Datastore, BigQuery, and Stackdriver, using the transition to re-architect core services. Although moving from its prior platform removed some built-in application metrics, Smash.gg recreated them through Stackdriver log-based metrics and BigQuery, and also assembled an interim asynchronous tracing workflow using logs, Pub/Sub, Cloud Functions, and the Trace API. After one month in production on GCP, the company reported roughly 10% lower costs without committed-use discounts, available capacity, centralized logging that accelerated troubleshooting, and improved ability for engineers across the team to handle DevOps work.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.