This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 1. Highest priority is to satisfy customer through early and continuous delivery of valuable software | |
| 2. Welcome changing requirements, even late in development | |
| 3. Deliver working software frequently | |
| 4. Business people and developers must work together daily | |
| 5. Build projects around motivated individuals |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| I. Codebase | |
| One codebase tracked in revision control, many deploys | |
| II. Dependencies | |
| Explicitly declare and isolate dependencies | |
| III. Config | |
| Store config in the environment | |
| IV. Backing services |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Serverless principles | |
| # General design principles to facilitate good design in the cloud for serverless applications | |
| * Speedy, simple, singular: | |
| Functions are concise, short, single purpose and their environment may live up to their request lifecycle | |
| * State Machines for Orchestration: | |
| Chained Lambda within code = Monolithic app vs using a state machine to orchestrate transactions and communication flows. | |
| * Think concurrent requests, not total requests: |