What problem does it solve? Misconfigured MongoDB connection pools cause pool exhaustion, connection churn, timeouts, and wasted server memory. This Skill guides you to size pools and set timeouts based on your actual deployment context instead of blindly applying arbitrary values. ## Core Features & Use Cases - Context-Driven Configuration: Gathers environment details (serverless vs. traditional, OLTP vs. OLAP, concurrency, traffic patterns) before recommending pool parameters with justified values. - Scenario-Based Recommendations: Provides tuned configurations for serverless functions, long-running OLTP servers, analytical workloads, and bursty high-traffic applications. - Troubleshooting Guidance: Diagnoses pool exhaustion, connection timeouts, connection churn, and high latency, distinguishing client configuration issues from infrastructure problems. - Use Case: A developer deploying a Node.js API on AWS Lambda gets a recommended configuration with maxPoolSize of 3-5, minPoolSize of 0, and client initialization outside the handler to enable connection reuse across warm invocations. ## Quick Start Ask the assistant to review your MongoDB client connection code and recommend an optimized pool configuration for your deployment environment.
