Chapter 2 / Application DesignApplication
Application
Architecture Design
Design apps to include not just build technology but performance, resilience, error behavior, security, API, and CI/CD.
8 Guidelines
The 8 items in this chapter
We summarize the design perspectives a continuously running app needs, from development to release.
1Language/FWChoose technology you can operate.
2PerformanceMeasure and improve.
3Availability/RedundancyMake it resilient and easy to recover.
4ErrorsDecide retries and timeouts.
5App securityProtect input, authentication, and secrets.
6DevOpsDeliver safely with CI/CD.
7API managementArrange entry, authentication, and limits.
8Fail-softKeep impact small even on failure.
Build / Performance / DevOps
Align build technology with operable technology
Choose languages and frameworks by maintainability, not just trends. Measure performance rather than guess, and deliver safely with CI/CD.
Choose languages and frameworks.Measure and improve performance.Automate testing and deployment with CI/CD.
Security / API / Fail Soft
Connect securely and keep running on failure
Include app security, API management, and fail-soft in the design, not as afterthoughts. Organize entry points and keep user impact small even on unexpected failures.
Decide authentication, authorization, input validation, and secret management.Decide API authentication, versioning, and rate limits.Decide fallback behavior and guidance for partial failures.
Build and measure
- Chose languages and frameworks.
- Decided performance targets and measurement methods.
- Decided availability and redundancy policy.
Protect and connect
- Organized app security perspectives.
- Decided API management rules.
- Decided authentication and usage limits.
Deliver and recover
- Decided error handling.
- Set up CI/CD.
- Decided fail-soft behavior.