Responsibility before tooling
We define what each layer must own before choosing its framework or database.
DEVNU / TECHNOLOGY INDEX
A stack only earns its place when there is a reason for it.
These pages are not dictionary definitions. They explain where we use each technology, what responsibility it owns, which trade-offs it creates, and when it should stay out of the architecture.
Discuss a projectReal maintenance cost
Every dependency, runtime and service has to create more value than the operational cost it adds.
Replaceable and documented
The stack should not lock the product to an undocumented choice or one developer.
Tools with a defined role in DEVNU architectures.
01
UI RUNTIME
02React
Frontend & interface engineering
WEB APPLICATION FRAMEWORK
03Next.js
Web applications & server rendering
APPLICATION LANGUAGE
04TypeScript
Application contracts & JavaScript engineering
SERVER RUNTIME
05Node.js
Backend runtime & server tooling
BACKEND APPLICATION FRAMEWORK
06NestJS
APIs, domain logic & backend services
AUTOMATION & DATA RUNTIME
07Python
Automation, data processing & specialist services
RELATIONAL DATA SYSTEM
08PostgreSQL
Relational data & transactional systems
DATA ACCESS & MIGRATIONS
09Prisma
TypeScript ORM, schema & migrations
IN-MEMORY DATA & QUEUES
10Redis
Caching, queues & ephemeral state
APPLICATION DELIVERY
11Docker
Service packaging & repeatable delivery
EDGE WEB SERVER
12Nginx
Reverse proxy, TLS & service ingress
DNS, CDN & EDGE
13Cloudflare
DNS, CDN, edge security & tunnels
CONTENT MANAGEMENT SYSTEM
WordPress
CMS for content-led sites & editorial teams
No technology is the product by itself.
Interface, rendering, state and indexable experiences.
Application logic, APIs, integrations and jobs.
Durable data, transactions, queries and ephemeral state.
Builds, networking, ingress, TLS and the edge.
When editorial workflow is the primary problem.
06 / NEXT STEP
If the stack is already decided, we should still verify why.
The best architecture is neither the smallest nor the largest stack. It is the one that covers the responsibilities without unnecessary complexity.
Describe the problem