A short deadline does not remove the need for architecture. It changes what the architecture must do: reduce uncertainty quickly enough that implementation can move without constant renegotiation.
Start with boundaries people can name
COFI Global Impact included projects, volunteering, donations, geospatial discovery, impact records, rewards, and branded media. I organised the backend around those business capabilities so ownership and dependencies were visible.
The architecture document was completed in four days. Its value was not its length; it gave the team a shared map for the remaining four weeks.
Move slow work off the request path
Media generation and branded assets do not belong inside an HTTP request. RabbitMQ, S3 events, and Lambda created a clear asynchronous path while the main application stayed responsive.
Queues also make failure a first-class concept. Retries, status, and observability can be designed around a job instead of hidden inside a request timeout.
Architecture earns its keep in delivery
The test of a design is whether it helps a team ship. A complete backend in four weeks came from choosing boundaries that supported parallel work and managed services that removed undifferentiated infrastructure effort.
