Architecture decision records
Format: MADR 4.0.0. This example uses the full template for decisions with real trade-offs.
| ID | Title | Status |
|---|---|---|
| 0000 | Use Markdown Architectural Decision Records | accepted |
| 0001 | PostgreSQL for trips and inventory | accepted |
| 0002 | Redis for station availability | accepted |
| 0003 | TimescaleDB for battery samples, not the trip store | accepted |
| 0004 | Node.js and Fastify for the API | accepted |
| 0005 | PostgreSQL reachable only from the API, with two roles | accepted |
| 0006 | Short bike hold in Redis, not a trip | proposed |
0001, 0002, 0004, and 0005 are the foundation of the first release. The numbers follow the order the files were added, not the calendar: 0004 and 0005 are dated March, with the other founding decisions. 0003 is the decision left behind by RFC 0001 when electric bikes were added.