Capture the "pain" that this tool relieves about mu HOT 3 CLOSED

From @PaulDuvall -

Now, a lot of it was new to me when I implemented most of what this framework would do, but it was many hundreds of lines of CloudFormation code (and lots of decisions) to get my ECS cluster, task definition, service, CodePipeline, (Jenkins), etc, etc. It was a PITA. I'd have to guess that it could take a few days of work for a competent engineer to put something like this together. But, the kicker is that they'd have to do it all over again for each new service and then maintain it. That's the selling point to me...

from mu.

I had a similar experience when working with ECS in that it is a great set of resources for running microservices, but requires a fair bit of knowledge to get all the pieces working. For example, just to run the simple service in the blog post, here are the 3 CloudFormation templates I created:

• Environment
• Repository
• Service

That's over 500 lines of CloudFormation templates (not counting how much it'd take for CodePipeline+CodeBuild) that would be replaced by the 20 lines in the sample yaml in the README.

from mu.

20 YAML lines! I'm sold!

from mu.