Pando looks nice, thanks for sharing. Is this an overlay on e.g, AWS, or is the idea that this spins up a single container and creates partitions for each of the user apps its hosting?
It’s more of an orchestrator. Destinations are controlled through runtime “adapters” which essentially tell Pando where and how to put apps. Instead of partitioning a container, it creates an isolated network and deploys the different workloads of your app as containers (database, web, api, etc.)
Since it’s modular, the goal is to be able to use AWS, GCP, kubernetes, etc. as the destination for apps, if you are already using that.(not all of them are built yet). By default it uses Docker.
I wonder how much of that orchestration is necessary for a narrow use-case with low numbers of users. So many of our patterns are for a scale a small internal tool will never see.
Validating to see others trying to solve this problem too!