Architecture
How the app is put together.
Web Image Optimizer is split into a Next.js frontend, a FastAPI API, Celery workers, Redis, and private S3-compatible object storage. The API coordinates jobs; workers do the image processing.
System context
A website developer uploads one source image and receives optimized assets, code examples, and a downloadable ZIP for their own project.
Container view
The web app handles the interface, the API coordinates state and storage, workers run CPU-heavy image work, Redis stores temporary job state, and object storage holds private artifacts.
API component view
The API keeps HTTP routes thin, moves business rules into services, and isolates Redis/S3 access behind repositories and storage clients.
