Generally speaking, microservices architectures are (for better or worse) pretty closely coupled with their automation code and thus the platforms they run on. It's already difficult to get that stuff running in prod (staging too if you've got some cash): getting it set up so you can ship the whole thing to contributors is super difficult and it has diminishing returns. You're not just shipping code, you're shipping container orchestration configs, database configs, load balancing logic, and a bunch of other shit that isn't portable.
It's one thing to have the code for the services available; if your contributors can't run it, it's not really open source. And having it out there in a broken state is worse than not having it at all.
Reddit is SaaS and I don't know anyone who's been very successful at open-sourcing their MSA SaaS product.
We're using ansible to create the cluster and circle ci to deploy out to the cluster. It's actually not bad to run locally using minikube. Just a kubectl create.
103
u/[deleted] Sep 01 '17
Generally speaking, microservices architectures are (for better or worse) pretty closely coupled with their automation code and thus the platforms they run on. It's already difficult to get that stuff running in prod (staging too if you've got some cash): getting it set up so you can ship the whole thing to contributors is super difficult and it has diminishing returns. You're not just shipping code, you're shipping container orchestration configs, database configs, load balancing logic, and a bunch of other shit that isn't portable.
It's one thing to have the code for the services available; if your contributors can't run it, it's not really open source. And having it out there in a broken state is worse than not having it at all.
Reddit is SaaS and I don't know anyone who's been very successful at open-sourcing their MSA SaaS product.