依赖Node.js require行为实现单例是否安全？附数据库连接池示例

Absolutely—this approach is totally safe, and it’s actually the de facto standard for creating singleton-style instances in Node.js, thanks to the platform’s built-in module caching mechanism.

Let me break down why this works reliably for your specific database pool example:

• When you first require('./db-instance.js') anywhere in your application, Node.js executes all the code in that module: it loads db-lib and db-config, creates the dbInstance connection pool, then stores that exported instance in its internal module cache.
• Every subsequent require call for the exact same module path will skip executing the module code again. Instead, Node.js just returns the cached dbInstance directly. So no matter how many times you import this module across different files, you’ll always get the same connection pool instance.

A few small caveats to keep in mind to avoid accidental duplicates:

• Stick to consistent module paths: Node treats paths as case-sensitive (on Unix-like systems) and will consider ./db-instance and ./DB-Instance as different modules, or ../utils/db-instance vs ./db-instance if called from different directory levels. Using inconsistent paths can bypass the cache and create multiple instances.
• Don’t mess with require.cache manually: If someone in your codebase explicitly deletes the entry for db-instance.js from require.cache, the next require will re-run the module code and create a new pool. But this is an edge case—normal application code shouldn’t be modifying the module cache unless you have a very specific reason.
• Instance validity is separate from caching: The require cache ensures you get the same object, but you’ll still want to make sure your database pool handles edge cases like dropped connections or reconnections properly. That’s a concern with the db-lib itself, not the singleton pattern via require.

Your current implementation is solid—this is exactly how Node.js is designed to work for shared, single-instance resources like database pools.

内容的提问来源于stack exchange，提问作者Gherman