Development – Triple-networks

Architecture decisions

How to quickly setup Architecture decisions for your project (directory)?

First, read https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions about following decisions without records (or documentation).

Then install the adr-tools (docs here): https://github.com/npryce/adr-tools/blob/master/INSTALL.md

Usage (readme):

adr help

cd ~/project-root

adr init docs/adr

adr new Implement as Unix shell scripts

adr new -s 9 Use Rust for performance-critical functionality

This will be a series about AWS services and their price from a developer’s perspective.

The question is:

Can I test this "AWS service" service without paying a lot of money?

Confidence in:

Build team-wide, deep understanding of each feature’s requirements and characteristics before coding starts
Expect collaborative, comprehensive grooming of features that include team and stakeholders
Ruthless slicing of features to smallest valuable increments
Write comprehensive automated unit tests in front-end and back-end layers
Shoot for high coverage from automated back-end integration tests
Shoot for high feature critical-path coverage from end-to-end UI tests
Include automated smoke tests that can be run on production-candidates
Ensure all post-commit tasks and hand-offs must be automated in CI/CD
Strive for quick, reliable rollback if smoke tests fail