Why not use console.log in production?
It is unstructured and slow. Use a logger like winston or pino. Log JSON with level, timestamp, and context. Ship logs to a central place for searching and alerting.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Common Architectural Mistakes in Node.js Projects
God modules, sharing databases across services, sync heavy work in request handlers, no API versioning, in-memory session state, tight coupling through direct imports, no schema validation, and console.log in production.
It couples services. If one service changes a schema, others break. Each service should own its data. If you need data from another service, use an API or event, not a direct query.
Offload heavy work to worker threads or background jobs. For long tasks, send a 202 Accepted and let the client poll for the result. Keep request handlers async and light.
Still have questions?
Browse all our FAQs or reach out to our support team