One company in SF using MeteorJS deploys a whole container with DB and everything per customer.
I think their primary reasoning is that Meteor doesn't scale super easy, so it was easier to just "shard" the whole stack per customer.
Personally, it's a lot of work. It depends on what you're doing to make the tradeoffs worthwhile.
I see this as an optimization. Build everything so you can deploy once for all your customers. If you need to shard by customer later, it's just an infrastructure problem.
I think their primary reasoning is that Meteor doesn't scale super easy, so it was easier to just "shard" the whole stack per customer.
Personally, it's a lot of work. It depends on what you're doing to make the tradeoffs worthwhile.
I see this as an optimization. Build everything so you can deploy once for all your customers. If you need to shard by customer later, it's just an infrastructure problem.