backend-patterns

Use resource-based URLs like GET /api/markets for lists and GET /api/markets/:id for single resources, with query parameters for filtering, sorting, and pagination. Separate concerns using the repository pattern for data access and a service layer for business logic.

Batch fetch related records instead of querying in a loop. Collect all foreign keys, run a single query to fetch related entities, then map them back in memory using a Map keyed by ID.

Cache-aside checks Redis first for a key, and on a miss fetches from the database and writes the result to Redis with a TTL. This keeps frequently accessed data like market records fast to retrieve while the database remains the source of truth.

Extract the Bearer token from the authorization header, verify it with jsonwebtoken against your JWT secret, and attach the decoded payload to the request. Wrap handlers in a withAuth middleware or call a requireAuth helper that throws a 401 ApiError on failure.

Use the repository pattern when you want to abstract data access behind an interface so business logic stays independent of the database. It is most valuable in larger codebases where you may swap implementations, such as moving from Supabase to another store, or need testable data layers.