@tumbaland/backend-core 1.55.0 → 1.56.0

package/dist/database/connection.d.ts

@@ -1,16 +1,16 @@
 import { ConnectOptions } from 'mongoose';
 /**
- * How the pool behaves toward a database that is across the internet.
+ * How the pool behaves, so a burst of requests does not pay for opening connections.
  *
- * Measured, not assumed: on the Pi a database lookup took about 17 ms on a warm
- * connection and 850 to 1,370 ms on a cold one, so the distance to Atlas is not
- * the cost. Opening a connection is. It is a TCP and TLS handshake and an
- * authentication, from a small machine, and the driver defaults make a burst of
- * requests pay for it badly:
+ * Measured, not assumed: against a database across the internet (the hosted one
+ * this replaced) a lookup took about 17 ms on a warm connection and 850 to
+ * 1,370 ms on a cold one, so distance was not the cost. Opening a connection was.
+ * It is a TCP and TLS handshake and an authentication, from a small machine, and
+ * the driver defaults make a burst of requests pay for it badly:
  *
  *  - It keeps no connections open, and an idle one is eventually dropped by
- *    something between here and Atlas, so the first request after a quiet spell
- *    starts from nothing.
+ *    something on the way, so the first request after a quiet spell starts from
+ *    nothing.
  *  - It opens at most two connections at a time. Opening a thread sends five or
  *    six requests at once, so they queued behind each other, a second or so per
  *    pair, and the thread took three to seven seconds.
@@ -20,8 +20,8 @@ import { ConnectOptions } from 'mongoose';
  *  - `maxConnecting` lets the pool open several at once when it does need more.
  *  - `maxIdleTimeMS` retires a connection that has sat idle for a few minutes,
  *    before something else kills it, and the pool opens a fresh one in its place.
- *  - `family: 4` skips the IPv6 half of every hostname lookup. Atlas is IPv4, and
- *    a resolver that is slow to answer for AAAA delays every new connection.
+ *  - `family: 4` skips the IPv6 half of every hostname lookup. The database is
+ *    IPv4, and a resolver that is slow to answer for AAAA delays every new connection.
  *
  * Each can be set per deployment, for a database that is somewhere else.
  */
@@ -29,12 +29,12 @@ export declare function poolOptions(env?: NodeJS.ProcessEnv): ConnectOptions;
 /**
  * Connects once and throws on failure. There is deliberately no retry loop here.
  *
- * MongoDB is Atlas (`mongodb+srv://`), not a sidecar container, so there is no
- * boot race to ride out — and the driver already retries for us: `connect()`
- * keeps doing server selection for `serverSelectionTimeoutMS` (30s by default)
- * before it rejects, so a transient DNS or network blip is absorbed there.
- * Anything that survives that is a real fault — bad credentials, an IP missing
- * from the Atlas allowlist, a dead cluster — and no amount of retrying fixes it.
+ * The driver already retries for us: `connect()` keeps doing server selection
+ * for `serverSelectionTimeoutMS` (30s by default) before it rejects, so a
+ * transient DNS or network blip, or a database container that is still starting,
+ * is absorbed there. Anything that survives that is a real fault — bad
+ * credentials, a wrong address, a database that is down — and no amount of
+ * retrying fixes it.
  *
  * Callers exit non-zero when this throws, which hands the problem to the
  * container restart policy (`restart: unless-stopped`) that already supervises

package/dist/database/connection.js

@@ -16,17 +16,17 @@ let connected = false;
 let pending = null;
 let listenersRegistered = false;
 /**
- * How the pool behaves toward a database that is across the internet.
+ * How the pool behaves, so a burst of requests does not pay for opening connections.
  *
- * Measured, not assumed: on the Pi a database lookup took about 17 ms on a warm
- * connection and 850 to 1,370 ms on a cold one, so the distance to Atlas is not
- * the cost. Opening a connection is. It is a TCP and TLS handshake and an
- * authentication, from a small machine, and the driver defaults make a burst of
- * requests pay for it badly:
+ * Measured, not assumed: against a database across the internet (the hosted one
+ * this replaced) a lookup took about 17 ms on a warm connection and 850 to
+ * 1,370 ms on a cold one, so distance was not the cost. Opening a connection was.
+ * It is a TCP and TLS handshake and an authentication, from a small machine, and
+ * the driver defaults make a burst of requests pay for it badly:
  *
  *  - It keeps no connections open, and an idle one is eventually dropped by
- *    something between here and Atlas, so the first request after a quiet spell
- *    starts from nothing.
+ *    something on the way, so the first request after a quiet spell starts from
+ *    nothing.
  *  - It opens at most two connections at a time. Opening a thread sends five or
  *    six requests at once, so they queued behind each other, a second or so per
  *    pair, and the thread took three to seven seconds.
@@ -36,8 +36,8 @@ let listenersRegistered = false;
  *  - `maxConnecting` lets the pool open several at once when it does need more.
  *  - `maxIdleTimeMS` retires a connection that has sat idle for a few minutes,
  *    before something else kills it, and the pool opens a fresh one in its place.
- *  - `family: 4` skips the IPv6 half of every hostname lookup. Atlas is IPv4, and
- *    a resolver that is slow to answer for AAAA delays every new connection.
+ *  - `family: 4` skips the IPv6 half of every hostname lookup. The database is
+ *    IPv4, and a resolver that is slow to answer for AAAA delays every new connection.
  *
  * Each can be set per deployment, for a database that is somewhere else.
  */
@@ -57,12 +57,12 @@ function poolOptions(env = process.env) {
 /**
  * Connects once and throws on failure. There is deliberately no retry loop here.
  *
- * MongoDB is Atlas (`mongodb+srv://`), not a sidecar container, so there is no
- * boot race to ride out — and the driver already retries for us: `connect()`
- * keeps doing server selection for `serverSelectionTimeoutMS` (30s by default)
- * before it rejects, so a transient DNS or network blip is absorbed there.
- * Anything that survives that is a real fault — bad credentials, an IP missing
- * from the Atlas allowlist, a dead cluster — and no amount of retrying fixes it.
+ * The driver already retries for us: `connect()` keeps doing server selection
+ * for `serverSelectionTimeoutMS` (30s by default) before it rejects, so a
+ * transient DNS or network blip, or a database container that is still starting,
+ * is absorbed there. Anything that survives that is a real fault — bad
+ * credentials, a wrong address, a database that is down — and no amount of
+ * retrying fixes it.
  *
  * Callers exit non-zero when this throws, which hands the problem to the
  * container restart policy (`restart: unless-stopped`) that already supervises

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tumbaland/backend-core",
-  "version": "1.55.0",
+  "version": "1.56.0",
   "description": "Core shared functionality for Tumbaland backend services",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",