- low cognitive overhead for the team
- fast delivery for the org
- reliable service for the org
- safety for our customers
- fewest moving parts possible
- most boring tools possible
- one-click, engineer-driven deployments
I hereby claim:
To claim this, I am signing this object:
What follows is a description of how one might reasonably manage the core configuration of a stateless service platform.
input- initial inputs that help describe a desired state. includes information such as allowed amis, application manifests, etc
compiler- reads inputs, produces cloudformation templates along with other top-level metadata. (important to note that there could even be multiple compilers)
metadata- top-level, global data that describes ideal state of the platform
What follows is a brief description of what comprises a general stateless service platform. It assumed that all stateful services live elsewhere (Heroku Postgres, AWS, etc).
This document aims to show you that a service platform can be built from a few simple ideas without need of anything highly complex or a lot of moving parts.