Sam doing a 180 on non-profit to for-profit was egregious, IMHO. Having said that, plenty of extremely profitable organizations masquerade (literally and figuratively) as non-profits.
I love the casual feel of this app. I would just keep this humming along in the background during code sprints and general digital (a)syncing with friends.
Hey, Tony. :)
I believe that COSS companies are extremely successful when they are able to build large and successful positive-sum and inclusive ecosystems around their FOSS core (specifically, that core being FOSS licensed, not source-available license'd). My partner Heather Meeker has written most of these non-compete licenses. They are useful at the crust around the core, not in the core, IMHO.. if they are applied to the core, there is very little distinguishing it from freemium/proprietary which != FOSS.
Also, many of the most successful COSS companies never raised a cent of VC to get to scale: Jetbrains, Liferay, Odoo, etc. and the ones that did raise a similar amount of money to get to scale did not really need it, they just accepted it along to way maybe to speed growth a bit, but their commercialization strategies were often working quite well and their customer acquisition costs highly efficient.
Envoy is an extremely exciting project. I've been following it closely since OSS inception and am thrilled to see the upcoming deep integration with the Kubernetes project. Such a natural and complimentary fit!
With flexibility as both a side car and host proxy network call fabric for polyglot distributed services, I see Envoy as a kind of modern ESB for the reincarnation of SOA we are seeing in the microservices movement. Congrats to the awesome contributors from Lyft/IBM/Google and others!
As long as your apps run well in containers (Docker or Rkt or others even), they can run and work well on K8s, which also runs well on AWS. You should consider K8s to replace imperative CM-based (Salt/Ansible) deployment mechanisms. The native pod abstraction in K8s can also nicely address multi-container composition issue you mentioned.
Minikube is awesome! We used it at Apprenda in a recent K8s 101 webinar (0). Standing up a local K8s cluster in 1-2 minutes is a really great experience.
I think the article provides some great foundational perspectives on how HA/service discovery/port mgmt and so on were handled in the "pre-containers" era of VMs with a look into how these challenges are somewhat re-imagined in this current world of containers (predominantly Docker). I'm looking forward to the follow-on post about why they chose Kubernetes and how that solution works for them.
Kubernetes is supported on AWS by various companies in the industry, including my own, Kismatic (the enterprise Kubernetes company). We have been pushing for the team at ECS to adopt K8S as a standard framework on which to run containerized workloads. As Kubernetes gets adopted as a container cluster management standard for orchestrating and running microservice-oriented apps, all the cloud providers will need to support it based on customer demand, in the same way they are all supporting Docker due to the demand.