De-cloud and de-k8s – bringing our apps back home
Regardless of the merits or drawbacks of &quot;de-clouding&quot; for this particular company, it seems to me that their ops team is just really bored or permanently unsatisfied with any solution.<p>They say that they&#x27;ve tried deploying their apps in all of:<p>* Their own Datacenter<p>* ECS<p>* GKE<p>* EKS<p>* and now back to their own Datacenter<p>Even with their new &quot;de-clouded&quot; deployment, it seems like they have created an absolutely immense amount of complexity to deploy what seems to be a variety of generic Ruby CRUD apps (I might be wrong but I didn&#x27;t see anything different in the post).<p>They have a huge list of tools and integrations that they&#x27;ve tried out with crazy names; Capistrano, Chef, mrsk, Filebeat, traefik...  It seems well on par complexity-wise with a full K8s deploy with all the bells and whistles (logging, monitoring, networking, etc.)<p>Google says that this company, 37signals, has 34 employees.  This seems like such a monumental amount of orchestration and infra stuff unless they&#x27;re deploying some crazy complex stuff they&#x27;re not talking about.<p>Idk what the lesson is here, if there is one, but this seems like a poor example to follow.