mongodb-connection

What problem does it solve?

This skill helps engineers and architects avoid misconfigured MongoDB clients by providing context-aware guidance for connection pooling, timeouts, and reuse patterns to prevent pool exhaustion, excessive connection churn, and performance regressions across official drivers.

Core Features & Use Cases

• Context-first recommendations: Prompts for deployment type, workload, concurrency, driver and server details before suggesting parameters.
• Scenario-driven presets: Practical settings and rationale for serverless functions, long-running servers (OLTP), OLAP/analytics, and high-traffic/bursty applications.
• Monitoring & troubleshooting: Guidance to instrument driver pool events and server metrics, interpret wait queue and connections.current, and act on ConnectionCheckOutFailed or rapid ConnectionCreated events.
• Use case: Convert a Lambda that repeatedly creates clients into a warm-reuse pattern with conservative maxPoolSize, sensible timeouts, and active monitoring to eliminate MongoWaitQueueTimeoutError.

Quick Start

Initialize a single MongoClient outside your serverless handler, set maxPoolSize to 5 and maxIdleTimeMS to 20000 to enable warm invocation reuse while monitoring wait queue and server connection metrics.