[dekz]

How do you feel Convox deals with the Hybrid approach? Of wanting to use a PaaS App container service, but keep the app dependencies like Cache, ElasticSearch DB hosted by AWS.

Does Convox continue to use hosted AWS services?

I like the idea of the App being containerised and that workflow, but I cannot convince myself that running DB/Cache in something like Convox is a good idea (vs Hosted in AWS).

Can you give your thoughts?

[nzoschke]

One of the core values of convox engineering is that services are better than software.

We do not run dbs as containers other than for dev or testing.

'convox services add postgres' and 'convox services add redis' provisions RDS and Elasticache respectively.

[dekz]

That is great. What about services which convox doesn't support (yet)?

For example SNS. Would convox ever support terraform/cloudformation for an App, or would you add SQS service in convox, then create SNS outside of convox, and then join them together somewhere else?

[nzoschke]

convox services add [sns|sqs|s3]

Is a thing.

Automatic provisioning services should be easy.

Your rack and all your apps and services are CloudFormation stacks. We favor CloudFormation over terraform for the same reason, it's a managed service.

The dream is fully automated provisioning of everything you want inside a single AWS account and VPC.

Then you can peer this VPC with another to keep linking things.

The framework is open source so it's pretty easy for us or anyone to add more services when requested. SES would be a good one next.