Mu

We will use Mu for this workshop. Why Mu?

It’s Opinionated

Mu takes all of the best practices learned from operating in many organizations and generates sensible boilerplate CloudFormation to support running your infrastructure and microservices.

It focuses on the developer experience

Mu keeps the developer experience simple, giving tools to get your microservice running as quickly as possible, and tools to support the developer troubleshooting problems with the microservices.

It’s Cloud Native

Mu knows when to stay out of the way. Mu only uses AWS resources for deploying your microservices.

Continuous Delivery

Mu uses CodePipeline and CodeBuild to continuously test and delivery your microservice to production.

Polyglot

Mu doesn’t have a favorite language. If you can get your microservice running with a Dockerfile, then mu can help!

Stateless

You are not locked in to using Mu. Mu doesn’t have any servers or databases running anywhere. Mu leverages CloudFormation to manage state for all AWS resources.

Declarative

Mu makes sure you get what you want. You declare your configuration in a YAML file and commit with your source code. Mu takes care of setting up your AWS resources to meet your needs.

Open Source

Mu is MIT licensed, so you can use it commercially. Mu is always looking to improve, so please consider contributing!

Mu only writes CloudFormation. To enhance developer experience, Mu also reads from the apis of CloudWatch, ECS, ECR and CloudTrail, using the local developer’s credentials.