Next.js and NestJS production
APPLICATION DELIVERYDockerService packaging & repeatable delivery
DEVNU / TECHNOLOGY / DOCKER
Docker is useful when it makes runtime repeatable, not when it merely makes commands longer.
Containers make each service's dependencies, network and startup boundary explicit. For VPS and multi-service systems, Docker Compose can provide understandable repeatable delivery without introducing Kubernetes on day one.
What does Docker own in a project?
In DEVNU production deployments, frontend, API and database commonly run as separate services on private networks; Nginx receives public traffic and the database port is not exposed. Image builds, environment variables, migrations and health checks are part of the release process.
Where the technology should solve a specific problem.
PostgreSQL on private networks
Workers and queue services
Staging and production environments
Reproducible builds
Controlled recreation and rollback
When we reach for it
Multiple services, native dependencies, VPS delivery, staging/production parity and rebuild/rollback needs are strong fits. Compose also improves handoff because service topology is recorded as code.
When we leave it out
For a simple static site on a platform that already manages builds and CDN delivery, containers may add no value. Docker also does not replace configuration management, backups or monitoring.
Using the tool is easy. Operating it well is the real work.
- 01Multi-stage builds
- 02Small images with production-only dependencies
- 03Real health checks
- 04Secrets kept out of images
- 05Volumes only for required state
- 06Explicit public/private networks
The decisions matter more than the stack badge.
Compose or Kubernetes?
Until multi-node orchestration, autoscaling or complex rollouts are genuinely required, Compose on a VPS is often simpler and easier to operate.
Database in a container?
It can be, provided volumes, backups, upgrades and recovery are explicit. Containerising a database does not remove state-management responsibilities.
Use the latest tag?
Production dependencies should usually be pinned by version or digest so tomorrow's rebuild does not silently differ from today's.
Projects where Docker is part of the recorded stack.
Industrial website & content administration
SUMY Website & Operations System
SUMY's bilingual industrial website, with an API, database and a dedicated admin area for pages, products, brands and incoming enquiries.
- React
- TypeScript
- NestJS
- PostgreSQL
- Prisma
- Docker
Telegram bot, Mini App & order automation
PasarGuard — Telegram commerce & operations
A personal product that brings ordering, wallet balance, service delivery and reseller operations into one Telegram bot and Mini App flow.
- Telegram
- React
- TypeScript
- FastAPI
- PostgreSQL
- Redis
- Docker
- Nginx
Messaging product, Android & relay infrastructure
ChatNU — Lightweight Deployable Messenger
A simple Android messenger built around WebSocket and relay communication, designed for fast deployment, low-friction use, and constrained connectivity environments.
- Android
- Kotlin
- WebSocket
- Node.js
- PostgreSQL
- Docker
07 / RELATED SERVICES
Technology only matters inside a useful outcome.
Common questions about Docker
01Does DEVNU use Docker for every project?+
No. If the hosting platform already manages the runtime or the project is very simple, containers may not be necessary.
02Does Docker secure the server by itself?+
No. Firewalls, SSH, image hygiene, secret management, network exposure and patching remain separate operational concerns.
09 / NEXT STEP
Start with the problem. Choose the stack second.
If the project needs this technology, the reason should be visible in architecture, performance, user experience or maintenance cost.
Describe the project