slayerjain

Even on cloud - What do you think about running shared infrastructure (multi tenancy) vs running every customer on separate instance managed by us?

$100k Annually per customer on avg. Around 3 months of our customer's Data is 200GB.

I currently have a mix of both. Mostly shared but some dedicated for only the ones who absolutely needs it (majorly due to regulatory restrictions).

However, like you said separate instances is easier to setup but I'm afraid of the extra management hassle of managing 500 different instances (including different micro-services, DBs, etc)

Multi tenancy has introduced a lot of config flags to enable/disable features for different customers - since they wont all agree to switch at the same time.

Both approaches have their pros/cons. I'd love to find a place to read about people's experience like you with both approaches.

Yes, but it's not on the Appstore and having shortcuts is also handy :)

I didn't think of this. Thanks for sharing!

Thanks and We have that in our pipeline for a future release :)

docker-compose is typically not recommended for production, and if you do end up using it - do check out the production guide - https://docs.docker.com/compose/production/

I think we've developed multiple layers in our infrastructure (Cloud Infra - AWS, GCP.., Paas - Kubernetes, ECS.., Service mesh - Istio, linkerd.., application containers..). So it depends on how many layers you have and how you want to manage a particular layer. Companies at `any` scale can get away with just using Google App Engine (Snap) or have 5+ layers in their infrastructure.

I find Jenkins X really interesting for my applications. It seems to solve a lot of issues related to CI/CD and automation in Kubernetes. however, still lacks multi-cluster support.

Just applied :)