327 karma · joined July 9, 2011
One big reason to use Marathon + Chronos + Mesos is to get multi-tenancy of compute and data workloads on your instances. You can't get that with web-service specific tech like Tutum.
[1] appuri.com
[1] Appuri (www.appuri.com)
Pros: - Logical isolation. You can put instances (and RDS, Redshift) etc. inside logical subnets that are not addressable from the outside world. - VPNs. If you really want extra security, you can wire up VPN so one of your VPC subnets shows up on your corporate subnet.
Cons: - A complete pain to manage with SSH-based tools. Most deployment tools (Ansible, for example) and even lower-level tools like fleetctl don't play well (if at all) with jump boxes. Example - Ansible Tower requires instances that are publicly addressable OR placing a Tower instance inside a VPC (which means we can't use it to manage multiple VPCs) - We have had to write our own workarounds for the above con. - Complexity. There are more concepts to learn about. - Lack of portability. I don't know if all cloud providers (Azure, DO etc.) even support VPCs the same way AWS does. This makes our infrastructure less portable than I'd like
Contact me at bilal at careercup dot com, I will help you out pro bono.
I can see us using Terraform when it is a little more mature - basically more AWS providers. Give it 2 to 3 months :)
Also, does it export templates to CloudFormation? I'm wary of using a SaaS to manage my infrastructure if it doesn't give me a way to revert to core AWS services.