Disclaimer work at AWS.

I'm still trying to understand the scaling story better. When we say serverless it mentions automatically scaling when it detects some sense of resource pressure. If I have a "hot tenant-database", does that mean this shard will be scaled automatically without impact to existing queries? Or would there be some "blip". I suppose it's unavoidable in edge cases but curious about the regular ones as well.

It's an incredibly cool CX you have here with the automated query routing/tenancy story though, looking forward to what happens in this space.