Why you should care about this project:
You wouldn't spend months building your own Linux distribution, so why spend time reinventing the wheel with chef/puppet/ansible?<p>We're not building a PaaS. Like a Linux distribution, we're integrating open source building blocks (logging, service discovery, scheduling) so that you can focus on app development and analytics instead of sysadmin tasks.<p>I'll be giving a talk to the NYC Mesos user group this Wednesday June 17th: <a href="http://www.meetup.com/Apache-Mesos-NYC-Meetup/events/222932873/" rel="nofollow">http://www.meetup.com/Apache-Mesos-NYC-Meetup/events/2229328...</a>
In ansible.cfg, is a default of "host_key_checking = no" and "record_host_keys = no" a good idea? Shouldn't one ship things as secure by default and let the user disable host keys?
\tangent apps->webapps => libs->microservices?<p>They have the same non-technical <i>business</i> benefits, of charging per-usage, preventing piracy and decompilation/reverse-engineering etc.<p>Although microservices are more trouble to manage and have more (serialization/transport) overhead than a local lib, if it's all hosted in the same cloud, it can be OK - and even a multicore advantage (if you can parallelize).<p>I'd expect cloud providers and library/service vendors to be pushing microservices, even when the purely technical benefits don't quite add up...