Julien Bisconti - Google Developer Expert for Google Cloud


The journey from startup to international company is not so straight forward. In this talk, we will go through some of the most common pitfalls I’ve seen when scaling infrastructure and companies.There is no one size fit all, understanding the tradeoffs is important. This is what this talk is about: tradeoffs.We are going to peel down many layers of abstraction and estimate the total cost of ownership for the various services offered by GCP. Should we use kubernetes ? How to scale an application? How to scale a team? What tools helps you to scale? Is a microservices architecture good to start with?Those questions do not have a straight answer but we are going to see in which case it makes sense to use a particular technology.

My personal definition of “at scale” means a service handles more than 10,000 RPS (ten thousands requests per second). The reason I came up with that number is when I learned that the C10K problem is a solved problem and hardware is not the bottleneck anymore. Meaning that a single machine can handle 10,000 connections at the same time. If a single machine can handle that much, why build a distributed system ?