Technique
to get an idea of what to change
Tooling
you can use to start, and where to get help
Purpose
Why you might do this
Not my model, but I like it.
https://c4model.com is the canonical source of info
Context
Should be readable by non-technical users
Who are the users?
What does it do for its users?
What services does it talk to, to do this?
Containers
Aimed at technical audiences
What technologies are being used?
How do they talk to each other?
What does a deployment look like?
Components
Aimed at technical audiences
What libraries are in use?
Where are the boundaries between parts of a system?
Which bits of the codebase are ours?
Code (or classes)
Aimed at technical audiences
How is it implemented?
Which API methods are public?
Insert best practices for $LANG here
many workloads are spiky or drop to zero for extended periods… applications used in the workplace may only be active for 40 of the 168 hours in a week.
Adrian Cockroft
@adrianco: AWS, ex Netflix
Pricing | Bare Metal | Iaas / PaaS | FaaS |
---|---|---|---|
Compute | Entire Server | VPS, Dynos, Containers, etc. | Lambda |
Storage | Physical disks | Virtual Volumes | S3 |
Database | Your own Db Server | AWS Aurora RDS, Cloud SQL | AWS Aurora Serverless |
twitter: @climateActTech
also join the slack!