Gerhard Lazu

Maybe someone listening to this will tell me, hey Gerhard, you're wrong.

I would love to know that, seriously.

So the way I solved it is we deploy in all the regions, right?

Because you specify the size once, right?

So say my starting size is the large instance type.

It has a certain number of cores, certain number of memory.

And by the way, the disk is the same in all of them because that's like another problem.

So we will sidebar that or put a pin in that.

So when it comes to the initial deployment, you deploy the one size across all the application instances.

And then you go and need to check to see which instances should be scaled down.

so that you have the capacity, but the regions that don't need the capacity, you can just bring them down.

And you do like a rolling deploy in that you replace one for one, you have plenty of capacity to handle the traffic while instances are being rolled, all that good stuff.

but we have hot regions and we have cold regions.

And there's quite a few things here.

Again, if someone knows how to do this better, I would love to hear about that.

And we have the TOML, we have the primary region.

There's a couple of things here.

We'll come back to services and HTTP services.

That's a fun one.

We'll leave that for a little bit later.