I often find myself what "at scale" means. It is used by so many different providers and it gets confusing. When all you give the service is a container, how d

I often find myself what "at scale" means. It is used by so many different providers and it gets confusing. When all you give the service is a container, how dos it know how to scale your project? I presume it gives it more CPU and more RAM automagically but does that really provide "at scale" I think of "at scale" to mean really a lot of traffic. Spinning up new instances if your container is possible, but I think I would like an API where code can somehow interact with the scaling mechanism. I guess "stateless" gives us some information.