backend-dev

Use plural nouns for resources like /users, HTTP verbs for actions, and correct status codes such as 201 for creation and 422 for business rule violations. Return a consistent response envelope with data, error, and meta fields, and add pagination for list endpoints.

Follow the layered pattern: Route → Controller → Service → Repository → Database. Keep business logic in the service layer, not in controllers or models, so it stays testable and reusable across endpoints.

Use cursor-based pagination for datasets over 10K records since it stays performant as data grows. Offset pagination is simpler but degrades at large offsets, so reserve it for small admin-facing lists.

Normalize first and denormalize only for proven performance needs. Index foreign keys, add created_at and updated_at timestamps to every table, use soft deletes for important data, and always change schemas through migration files.

Use idempotency keys for non-idempotent POST operations like payments, order creation, and email sends. The server stores the key-to-result mapping for 24 hours so duplicate requests return the original result without side effects.