Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Hi there 👋,
Happy to hear that you’ve liked the App Platform so far!
To answer your questions:
doctl CLI tool to do this programmatically:https://docs.digitalocean.com/products/app-platform/how-to/scale-app/
The traffic will be automatically load-balanced across the containers, so you will not have to do any changes on your end. Except if your app uses sessions, then in this case it would be best to use a service like Redis to store your sessions there so that they could be shared across all containers.
As the storage of the containers in the App Platform is ephemeral, meaning that no data is persisted across restarts, I would suggest using an S3 storage to store your logs like the DigitalOcean Spaces. Or if you don’t need to persist your logs, as you mentioned you could create a web-based way of accessing them while they are still available inside the containers.
UPDATE: The App Platform now supports CPU based autoscaling:
https://www.digitalocean.com/blog/introducing-cpu-based-autoscaling-app-platform
Hope that this helps!
Best,
Bobby