@architect/docs
Advanced tools
Comparing version 30.0.11 to 30.1.0
# Concepts | ||
Cloud functions surface unique problems. | ||
Cloud functions surface unique problems: | ||
@@ -99,3 +99,3 @@ - Configuration tooling was designed for the last generation of metaphors (and lags behind the releases of new functionality) | ||
`architect` practice follows many of the principles pioneered by agile and championed by devops. We know its a good idea to version our infrastructure. We know we need tight feedback loops for dev. We need isolation between our development stages. And most of all we need our systems to be transparent and exensible. | ||
`architect` practice follows many of the principles pioneered by agile and championed by devops. Versioning infrastructure. Tight feedback loops for dev while maintaining isolation between stages. Systems that are consistent, inspectable, transparent and exensible. | ||
@@ -105,3 +105,4 @@ ### Architecture as Text | ||
- `.arc` manifest file defines achitecture element in the plainest text possible | ||
- Nesting is deliberately constrained | ||
- Nesting and syntax is deliberately constrained | ||
- And comments! | ||
@@ -118,2 +119,3 @@ ### Repeatable and Consistent Builds | ||
- `arc-deploy` treats `staging` and `production` as first class concepts | ||
- deployment to `production` requires an extra manual step of setting `ARC_DEPLOY=production` env var | ||
@@ -120,0 +122,0 @@ ### Extensible and Flexibile Systems |
@@ -9,3 +9,3 @@ # Limits | ||
- This means: you HAVE to consider retrys including manual retrys where you create/destory/recreate infra workflows (and accordingly `.arc` workflows are intended to be run and rerun) | ||
- Yes: I guess it is "kinda gross"! But: it works. Call this condition *immutable infrastructure* and maybe you'll feel better about it? 💖 | ||
- Yes: it is "kinda gross" but it works. Sometimes we call this situation *immutable infrastructure* to feel better! 💖 | ||
- Regions go down and there isn't really a great way beyond a DNS change window to move them | ||
@@ -22,3 +22,3 @@ - Lambda cold starts are vicious on large lambdas; the best antidote is to author small as possible lambda functions (rule of thumb: sub 5mb is sub second) | ||
File these things as: maybe someday. Many of these constraints where out of bare neccessity of speed aided by attempts to arrive an sort of minimum possible essentials. These items will be great topics of community discussion and future contribution. | ||
File these things as: _maybe someday_. Most of these constraints where borne out of neccessity for speed; velocity aided by way of minimum essential capability. These items will be great topics of community discussion and future contribution. | ||
@@ -25,0 +25,0 @@ - `PATCH`, `PUT`, `DELETE` are not suppported but maybe they shouldn't be (100% support everthing browsers do: `GET` and `POST` ;) |
@@ -7,6 +7,6 @@ # Roadmap | ||
- `arc-sandbox` error traps for 302, 403, 404 and 500 | ||
- `arc-functions` conslidate req/res impl | ||
- `text/javascript` and `text/css` route handlers | ||
- `arc-env` infra env var and configuration management | ||
- `text/javascript` and `text/css` route handlers | ||
- `arc-docs`: examples and guides | ||
- `arc-docs`: examples, guides, crsf and url helpers | ||
@@ -13,0 +13,0 @@ ## Ongoing and Future Scope |
@@ -19,6 +19,6 @@ # Introduction | ||
- It can be a nebulous Cloud. Even the errors are eventually consistent! Failure is common, expected really, and software needs to bake in service discovery, retry logic | ||
- Elastic scaling of server instances often just load balanced monolithic applications | ||
- It can be a nebulous Cloud: even the errors are eventually consistent! Failure is expected and software needs to bake in service discovery and retry logic | ||
- Setting up the infrastructure is difficult, time consuming and complex | ||
- Full deployment cycles with zero downtime take a long time to complete | ||
- Elastic scaling instances often just load balancing fleets of monolithic applications | ||
- Full deployment cycles across a fleet with zero downtime can take a very long time to complete | ||
- Costly billing and rising costs (smallest unit of compute is your entire app) | ||
@@ -25,0 +25,0 @@ |
{ | ||
"name": "@architect/docs", | ||
"version": "30.0.11", | ||
"version": "30.1.0", | ||
"main": "index", | ||
@@ -5,0 +5,0 @@ "scripts": { |
55461