barkibu-kb 1.2.0 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9b46793e55bdd7e53d2e98e3e792972ec67a86048074aeec1bc9ffdde8028965
-  data.tar.gz: 44d5748d6fb445709add87f4bea42c9c19516ff9bb81be8b4112b716c17469c9
+  metadata.gz: 5edd7ddce6b2d27e72f6cafcfb8efba18c35c001efe54ce96eb7a51a83d1d8ae
+  data.tar.gz: 7d1be392c9297f09f8420258adf07ad3b69b7f57d7a6a07210ef9f250aeb193e
 SHA512:
-  metadata.gz: 38cb22fa193c859a72448aea1cecfbad17671a4deae2dbd5763881c05f3ffa7338ab80b6218de5e041463c1e0575d190bba204fcf6851a6655107b1894eb1ca6
-  data.tar.gz: f66b4353ac4cc0e3432310ecf7d54b212dfe8b1b245ca6f9f95062b49185acc5028ac1b5ab69503f9099de9cfc89f2ff39e3c62df12531e8c4f593a3bef2e034
+  metadata.gz: 5427db71ffb7d349463fa04291f24106676b1761ea9e55c5cc0c0440e424dd8c5da57a70dbc17a7528f3e79a37dbe9f0ac57e80f6d735661c984eaf31b3b21a2
+  data.tar.gz: 2c92ff67fe128d0d5d9ae10e575e2df5d95d73945dbe10534aba6a6f1e493829fe09f8f0cb0613300f8b7318c73a46828139ea6a9098f6b15aa113b0f963d136

data/CHANGELOG.md

@@ -6,7 +6,18 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [unreleased]
-- See diff: https://github.com/barkibu/kb-ruby/compare/v1.2.0...HEAD
+- See diff: https://github.com/barkibu/kb-ruby/compare/v1.4.0...HEAD
+
+## [1.4.0]
+- Reuse connections to KB (keep-alive) with the stock faraday-net_http_persistent adapter. New runtime dependencies: `faraday-net_http_persistent ~> 1.2`, `net-http-persistent ~> 4.0` (4.0.8 accepts `connection_pool` 2.2.4 up to < 4). On by default; `KB.config.request.keep_alive = false` restores one connection per call. New `KB.config.request.idle_timeout` (default 30s, below the Heroku router's ~55s idle close).
+- Every `KB::Client` now shares one Faraday connection (`KB::Connections`), so all model clients use one connection pool per process. Clients send full URLs and their own `x-api-key` header per request; URLs, headers and cache keys are unchanged. Settings are read when that connection is built, on the process's first KB call; `KB::Connections.reset!` applies later changes.
+- A call with its own `read_timeout:` goes through a separate plain net_http connection, so its override never reaches the shared pool's other calls.
+- With keep-alive, a connect timeout is `Faraday::TimeoutError` (was `Faraday::ConnectionFailed`) wrapping `Net::OpenTimeout`, and a refused connection is `Faraday::ConnectionFailed` wrapping `Net::HTTP::Persistent::Error`. Both still become `KB::Error` in model calls and are still retried for every verb: `KB::RetryPolicy.root_cause` unwraps `Net::HTTP::Persistent::Error` to the underlying `Errno`. Datadog `error.type` on connect-timeout spans changes accordingly.
+
+## [1.3.0]
+- Retry transport failures once (`faraday-retry`, already in the Faraday 1.10 bundle, now an explicit dependency). `KB::RetryPolicy` decides by the underlying error, not the Faraday class: failures where the request never left (`Net::OpenTimeout`, `ECONNREFUSED`, `EHOSTUNREACH`, `ENETUNREACH`, `EADDRNOTAVAIL`, `SocketError`) retry for every verb; any other transport failure (read/write timeout, reset, EOF, TLS) retries for GET/HEAD only (and not when the call raised its own `read_timeout:`, so a 30s read isn't doubled); HTTP error responses never retry. New settings `KB.config.request.retries` (default 1, 0 disables) and `retry_interval` (default 0.1s, randomized up to 2x). Worst-case latency is now two attempts' worth of phase budgets.
+- `request.kb_client` payload gains `retries` and `retry_errors` on retried calls; the Datadog subscriber tags them as `kb.retries` / `kb.retry_errors`. The event and span cover all attempts, so a call that succeeded on retry is not an error.
+- `KB::Listable.all` (and so `PetParent.all`, `Pet.all`, `Breed.all`, `Product.all`, `Plan.all`, `Assessment.all`) now wraps `Faraday::ConnectionFailed` in `KB::Error` like every other model call, instead of re-raising it raw. Code rescuing `Faraday::ConnectionFailed` around `.all` must rescue `KB::Error` instead; none of Funnel, Global Admin or connected_health does.
 
 ## [1.2.0]
 - `KB::Client` emits one `request.kb_client` `ActiveSupport::Notifications` event per KB call (`KB::Client::REQUEST_EVENT`), wrapping cache lookup, connect, TLS, write, read and parsing. Payload: `verb`, `path`, `base_url`, `cache_hit` (GET only), `status`, plus ActiveSupport's `exception`/`exception_object` when the call raised. Every public method now goes through one private `perform` seam; no behaviour change (same cache keys, params and error classes).

data/Gemfile.lock

@@ -1,17 +1,20 @@
 PATH
   remote: .
   specs:
-    barkibu-kb (1.2.0)
+    barkibu-kb (1.4.0)
       activemodel (>= 4.0.2)
       activerecord
       activesupport (>= 3.0.0)
       dry-configurable (~> 0.9)
       faraday
       faraday-net_http (~> 1.0)
+      faraday-net_http_persistent (~> 1.2)
+      faraday-retry (~> 1.0)
       faraday_middleware
       i18n
-    barkibu-kb-fake (1.2.0)
-      barkibu-kb (= 1.2.0)
+      net-http-persistent (~> 4.0)
+    barkibu-kb-fake (1.4.0)
+      barkibu-kb (= 1.4.0)
       countries
       sinatra
       webmock
@@ -109,6 +112,8 @@ GEM
     multipart-post (2.3.0)
     mustermann (3.0.0)
       ruby2_keywords (~> 0.0.1)
+    net-http-persistent (4.0.8)
+      connection_pool (>= 2.2.4, < 4)
     parallel (1.24.0)
     parser (3.3.0.5)
       ast (~> 2.4.1)

data/README.md

@@ -74,14 +74,84 @@ and write budgets stay global:
 KB::Pet.kb_client.request('birthdays', filters: { month: 9, day: 22, size: 1000 }, read_timeout: 30)
 ```
 
+#### Retries
+
+The client retries a failed call once when the failure is in the transport, never
+when KB answered with an HTTP error. Which calls retry depends on whether the
+request can have reached KB (`KB::RetryPolicy`):
+
+| Failure | Retried for |
+|---|---|
+| Never sent: connect/TLS timeout (`Net::OpenTimeout`), connection refused, host/network unreachable, DNS failure | every verb, POST included |
+| Maybe sent: read/write timeout, connection reset, EOF, TLS error mid-stream | GET and HEAD only |
+| HTTP 4xx/5xx | never |
+
+PUT and DELETE are not retried on "maybe sent" failures: `upsert` and
+`PetParent#merge!` are PUTs whose second run is not a no-op on KB's side, and a
+repeated DELETE would turn a success into a 404. A call that raised its own read
+budget (`read_timeout:` on `KB::Client#request`) is not retried on "maybe sent"
+failures either, so a 30s birthdays read can't become 60s; failures that never
+reached KB are still retried.
+
+```ruby
+# config/initializers/kb_ruby.rb
+KB.config.request.retries = 1          # default; 0 disables retries
+KB.config.request.retry_interval = 0.1 # default, seconds; each wait is 1x-2x this
+```
+
+Like the timeouts, these are read when the process's shared KB connection is
+built, i.e. on its first KB call, so set them in an initializer (or call
+`KB::Connections.reset!` after changing them at runtime).
+
+Worst case, a call now takes two attempts' worth of phase budgets plus the
+interval, e.g. a GET that read-times-out twice takes about 2 x (1 + 3 + 5)s with
+the default timeouts.
+
+#### Keep-alive connections
+
+KB calls reuse TCP/TLS connections instead of opening a new one per call, through
+the stock `net_http_persistent` Faraday adapter (net-http-persistent). Every
+model's client shares one Faraday connection (`KB::Connections`), so they all
+draw on one connection pool per process; each
+thread checks a connection out per call. A pooled connection idle for longer
+than `idle_timeout` is closed and reopened on the next call.
+
+```ruby
+# config/initializers/kb_ruby.rb
+KB.config.request.keep_alive = true # default; false opens a connection per call (net_http)
+KB.config.request.idle_timeout = 30 # default, seconds
+```
+
+Keep `idle_timeout` below the Heroku router's own idle close: it drops an idle
+client connection after about 55 seconds (measured against KB staging,
+2026-09-23). A connection the server already closed is noticed before the next
+request is written, and reopened. A close that races the request in the same
+instant can't be noticed: a GET is retried on a fresh connection (see Retries),
+a POST fails with `Faraday::ConnectionFailed` wrapping `EOFError`.
+
+Net::HTTP's own retry of idempotent requests stays off (`max_retries = 0`), so a
+PUT is never resent behind `KB::RetryPolicy`'s back.
+
+A call with its own `read_timeout:` goes through a separate plain connection,
+opened for that call: the pooled adapter keeps one timeout setting for the whole
+pool, where one call's override would reach other threads' calls.
+
+Differences from `keep_alive = false`: a connect timeout surfaces as
+`Faraday::TimeoutError` wrapping `Net::OpenTimeout` (retries classify it by that
+underlying error, so it is still retried for every verb), and a refused
+connection as `Faraday::ConnectionFailed` wrapping `Net::HTTP::Persistent::Error`.
+
 #### Instrumentation
 
 Every KB call emits one `request.kb_client` event through
 `ActiveSupport::Notifications`, wrapping the whole call: cache lookup, TCP
 connect, TLS, write, read and JSON parsing. The payload carries `verb`, `path`,
-`base_url`, `cache_hit` (GET calls only), `status` (when a response arrived) and
-ActiveSupport's `exception` / `exception_object` when the call raised. Subscribe
-to it for logging, metrics or anything else:
+`base_url`, `cache_hit` (GET calls only), `status` (when a response arrived),
+`retries` and `retry_errors` (only when the call was retried: the count, and the
+underlying error class of each failed attempt, e.g. `["Net::OpenTimeout"]`) and
+ActiveSupport's `exception` / `exception_object` when the call raised. The event
+covers the whole call including retries, so `exception` is set only when every
+attempt failed. Subscribe to it for logging, metrics or anything else:
 
 ```ruby
 ActiveSupport::Notifications.subscribe(KB::Client::REQUEST_EVENT) do |event|
@@ -110,8 +180,10 @@ tracer's own Net::HTTP spans nest under it. It inherits the app's service
 knowledge-base service either: it measures the client's whole call, not a KB
 operation. Resources are low-cardinality (`GET /v1/pets/birthdays`,
 `GET /v1/pets/?/contracts`). Tags: `peer.hostname` (the KB host used),
-`kb.method`, `kb.cache_hit` (GET calls only), `http.status_code`, plus the
-standard `error.type`/`error.message` when the call raises.
+`kb.method`, `kb.cache_hit` (GET calls only), `http.status_code`, `kb.retries`
+and `kb.retry_errors` (retried calls only), plus the standard
+`error.type`/`error.message` when the call raises. A span with `kb.retries` and
+no error is a failure the retry absorbed.
 
 Why not rely on the Net::HTTP tracer alone: faraday-net_http opens the socket
 before `Net::HTTP#request`, the method that tracer patches, so a connect timeout

data/barkibu-kb.gemspec

@@ -53,6 +53,9 @@ Gem::Specification.new do |spec|
   spec.add_runtime_dependency 'activesupport', '>= 3.0.0'
   spec.add_runtime_dependency 'faraday'
   spec.add_runtime_dependency 'faraday-net_http', '~> 1.0'
+  spec.add_runtime_dependency 'faraday-net_http_persistent', '~> 1.2'
   spec.add_runtime_dependency 'faraday_middleware'
+  spec.add_runtime_dependency 'faraday-retry', '~> 1.0'
   spec.add_runtime_dependency 'i18n'
+  spec.add_runtime_dependency 'net-http-persistent', '~> 4.0'
 end

data/lib/barkibu-kb.rb

@@ -21,6 +21,15 @@ module KB
     setting :connect_timeout, default: 1
     setting :write_timeout, default: 3
     setting :read_timeout, default: 5
+    # Retries after a transport failure, per KB::RetryPolicy. 0 disables retries.
+    setting :retries, default: 1
+    setting :retry_interval, default: 0.1
+    # Reuse connections to KB across calls (faraday-net_http_persistent, one pool
+    # per process, see KB::Connections). false opens a connection per call.
+    setting :keep_alive, default: true
+    # Seconds a pooled connection may sit idle before it is closed and reopened.
+    # Keep it below the Heroku router's idle close (about 55s, see README).
+    setting :idle_timeout, default: 30
   end
 end
 
@@ -29,6 +38,8 @@ require 'kb/inflections'
 require 'kb/cache'
 require 'kb/client_resolver'
 require 'kb/errors'
+require 'kb/retry_policy'
+require 'kb/connections'
 require 'kb/client'
 
 require 'kb/concerns'

data/lib/kb/client.rb

@@ -2,6 +2,7 @@ module KB
   class Client
     # Emitted once per KB call, wrapping cache lookup and the HTTP request.
     # Payload: verb, path, base_url, cache_hit (GET only), status (when a response arrived),
+    # retries / retry_errors (only when the call was retried, see KB::RetryPolicy),
     # plus ActiveSupport's exception/exception_object when the call raised.
     REQUEST_EVENT = 'request.kb_client'.freeze
 
@@ -74,7 +75,7 @@ module KB
     end
 
     def http(event, payload, read_timeout)
-      response = connection.public_send(event[:verb], event[:path], payload, &request_options(read_timeout))
+      response = send_request(event, payload, read_timeout)
       event[:status] = response.status
       response.body
     rescue Faraday::ClientError, Faraday::ServerError => e
@@ -82,11 +83,12 @@ module KB
       raise
     end
 
-    def headers
-      {
-        'Content-Type': 'application/json',
-        'x-api-key': api_key
-      }
+    def send_request(event, payload, read_timeout)
+      connection(read_timeout).public_send(event[:verb], url_for(event[:path]), payload) do |req|
+        req.headers[:'x-api-key'] = api_key # a symbol, so Faraday names it X-api-key, as the log filter expects
+        req.options.read_timeout = read_timeout if read_timeout
+        RetryPolicy.track(req, event, read_timeout)
+      end
     end
 
     def attributes_case_transform(attributes)
@@ -99,31 +101,18 @@ module KB
       attributes_case_transform(attributes).to_json
     end
 
-    def connection
-      @connection ||= Faraday.new(url: base_url, headers: headers, request: request_timeouts) do |conn|
-        conn.response :json
-        conn.response :raise_error
-        if KB.config.log_level == :debugger
-          conn.response :logger do |logger|
-            logger.filter(/(X-api-key:\s)("\w+")/, '\1[API_KEY_SCRUBBED]')
-          end
-        end
-        conn.adapter :net_http
-      end
-    end
-
-    def request_options(read_timeout)
-      return nil if read_timeout.nil?
-
-      ->(req) { req.options.read_timeout = read_timeout }
+    # The process-wide connection every client shares (see KB::Connections):
+    # keep-alive unless disabled, or unless this one call sets its own read_timeout.
+    def connection(read_timeout = nil)
+      Connections.fetch(keep_alive: KB.config.request.keep_alive && read_timeout.nil?)
     end
 
-    def request_timeouts
-      {
-        open_timeout: KB.config.request.connect_timeout,
-        write_timeout: KB.config.request.write_timeout,
-        read_timeout: KB.config.request.read_timeout
-      }
+    # The URL a Faraday connection on base_url would build for `path`, by Faraday's
+    # own joining rules ("" is base_url itself, anything else is relative to
+    # base_url + "/"), so sharing one connection across clients changes no URL.
+    def url_for(path)
+      @url_builder ||= Faraday::Connection.new(url: base_url)
+      @url_builder.build_exclusive_url(path).to_s
     end
   end
 end

data/lib/kb/connections.rb

@@ -0,0 +1,70 @@
+require 'faraday/net_http_persistent'
+
+module KB
+  # The Faraday connections behind every KB::Client, shared per process.
+  #
+  # Each model class has its own KB::Client (PetParent, Pet, Breed...). Sharing
+  # one Faraday connection between them means one adapter instance, so with
+  # keep-alive (the stock faraday-net_http_persistent adapter) one connection
+  # pool serves every client. Clients send full URLs and their own API key per
+  # request, so nothing on the connection is specific to one client; the pool
+  # keeps its sockets per host and port.
+  #
+  # Two connections:
+  # - keep-alive, for every call on the global timeouts;
+  # - plain net_http (a new connection per call), for calls that set their own
+  #   `read_timeout:`. The persistent adapter writes each call's timeouts onto the
+  #   shared pool object, where any thread's next checkout reads them, so a
+  #   per-call override there would leak into other threads' calls.
+  #
+  # Built on first use from KB.config; `reset!` applies later config changes.
+  module Connections
+    MUTEX = Mutex.new
+    @connections = {}
+
+    class << self
+      def fetch(keep_alive:)
+        @connections[keep_alive] || MUTEX.synchronize { @connections[keep_alive] ||= build(keep_alive) }
+      end
+
+      def reset!
+        MUTEX.synchronize { @connections = {} }
+      end
+
+      private
+
+      def build(keep_alive)
+        Faraday.new(headers: { 'Content-Type': 'application/json' }, request: timeouts) do |conn|
+          conn.request :retry, RetryPolicy.middleware_options
+          conn.response :json
+          conn.response :raise_error
+          log(conn) if KB.config.log_level == :debugger
+          adapter(conn, keep_alive)
+        end
+      end
+
+      # The block runs on every request, on the shared Net::HTTP::Persistent.
+      # faraday-net_http's configure_request also sets max_retries = 0 there, so
+      # Net::HTTP never retries on its own: retries belong to KB::RetryPolicy.
+      def adapter(conn, keep_alive)
+        return conn.adapter(:net_http) unless keep_alive
+
+        conn.adapter(:net_http_persistent) { |http| http.idle_timeout = KB.config.request.idle_timeout }
+      end
+
+      def log(conn)
+        conn.response :logger do |logger|
+          logger.filter(/(X-api-key:\s)("\w+")/, '\1[API_KEY_SCRUBBED]')
+        end
+      end
+
+      def timeouts
+        {
+          open_timeout: KB.config.request.connect_timeout,
+          write_timeout: KB.config.request.write_timeout,
+          read_timeout: KB.config.request.read_timeout
+        }
+      end
+    end
+  end
+end

data/lib/kb/instrumentation/datadog.rb

@@ -72,9 +72,21 @@ module KB
 
           span.set_tag('kb.cache_hit', payload[:cache_hit].to_s) if payload.key?(:cache_hit)
           span.set_tag('http.status_code', payload[:status].to_s) if payload[:status]
+          tag_retries(span, payload)
           span.set_error(payload[:exception_object]) if payload[:exception_object]
           span.finish
         end
+
+        private
+
+        # Only on retried calls: `kb.retries` (numeric) and the distinct underlying
+        # errors that triggered them, e.g. `Net::OpenTimeout`.
+        def tag_retries(span, payload)
+          return unless payload[:retries]
+
+          span.set_tag('kb.retries', payload[:retries])
+          span.set_tag('kb.retry_errors', payload[:retry_errors].uniq.join(','))
+        end
       end
     end
   end

data/lib/kb/models/concerns/listable.rb

@@ -11,8 +11,6 @@ module KB
         kb_client.all(filters).map do |pet_parent|
           from_api pet_parent
         end
-      rescue Faraday::ConnectionFailed => e
-        raise e
       rescue Faraday::Error => e
         raise KB::Error.from_faraday(e)
       end

data/lib/kb/retry_policy.rb

@@ -0,0 +1,92 @@
+require 'socket'
+require 'net/http'
+require 'net/http/persistent'
+require 'faraday/retry'
+
+module KB
+  # Decides which failed KB calls the client retries.
+  #
+  # Two classes of transport failure, told apart by the underlying Ruby error
+  # rather than the Faraday class (adapters disagree on the Faraday class: the
+  # net_http adapter wraps Net::OpenTimeout as ConnectionFailed, the persistent
+  # one as TimeoutError):
+  #
+  # - never sent: TCP connect / TLS handshake did not complete, so KB cannot have
+  #   seen the request. Safe to retry for every verb, POST included.
+  # - maybe sent: anything else the transport raises (read/write timeout, reset,
+  #   EOF, TLS error mid-stream). KB may have processed it, so only GET/HEAD are
+  #   retried. PUT/DELETE are left out on purpose: `upsert` and `merge!` are PUTs
+  #   whose second run is not a no-op on KB's side, and a repeated DELETE would
+  #   turn a success into a 404.
+  #   A call that raised its own read budget (`read_timeout:`, e.g. 30s for
+  #   birthdays) is not retried on these either, so its worst case isn't doubled.
+  #
+  # HTTP responses (4xx/5xx) are never retried: KB answered.
+  module RetryPolicy
+    NOT_SENT_ERRORS = [
+      Net::OpenTimeout,
+      Errno::ECONNREFUSED,
+      Errno::EHOSTUNREACH,
+      Errno::ENETUNREACH,
+      Errno::EADDRNOTAVAIL,
+      SocketError # DNS resolution
+    ].freeze
+    TRANSPORT_ERRORS = [Faraday::ConnectionFailed, Faraday::TimeoutError, Faraday::SSLError].freeze
+    MAYBE_SENT_VERBS = %i[get head].freeze
+
+    module_function
+
+    def retry?(verb, error, own_read_budget: false)
+      return false unless TRANSPORT_ERRORS.any? { |klass| error.is_a?(klass) }
+
+      not_sent?(error) || (MAYBE_SENT_VERBS.include?(verb) && !own_read_budget)
+    end
+
+    def not_sent?(error)
+      cause = root_cause(error)
+      NOT_SENT_ERRORS.any? { |klass| cause.is_a?(klass) }
+    end
+
+    # The Ruby error behind a Faraday error. `wrapped_exception` is Faraday's own
+    # explicit link to it (Ruby's `cause` is only whatever was being rescued at
+    # the raise, usually the same object). Faraday's adapters wrap the Ruby error
+    # one level deep, so one level is enough, except that net-http-persistent
+    # re-raises a refused connection as its own Net::HTTP::Persistent::Error with
+    # the Errno as its `cause`.
+    def root_cause(error)
+      cause = (error.respond_to?(:wrapped_exception) && error.wrapped_exception) || error.cause || error
+      cause.is_a?(Net::HTTP::Persistent::Error) && cause.cause ? cause.cause : cause
+    end
+
+    # Options for faraday-retry's middleware, read from KB.config.request.
+    def middleware_options
+      {
+        max: KB.config.request.retries,
+        interval: KB.config.request.retry_interval,
+        interval_randomness: 1, # 1x-2x the interval, so a burst of callers doesn't retry in lockstep
+        exceptions: TRANSPORT_ERRORS,
+        methods: [], # always ask retry_if
+        retry_if: lambda do |env, error|
+          retry?(env[:method], error, own_read_budget: env[:request].context&.dig(:kb_own_read_budget))
+        end,
+        retry_block: ->(env, _options, _retries_left, error) { record(env, error) }
+      }
+    end
+
+    # Hands the request.kb_client event payload (and whether the call set its own
+    # read budget) to the middleware through the request context, so each retry
+    # is reported on the call's own event.
+    def track(request, event, read_timeout = nil)
+      tracking = { kb_event: event, kb_own_read_budget: !read_timeout.nil? }
+      request.options.context = (request.options.context || {}).merge(tracking)
+    end
+
+    def record(env, error)
+      event = env[:request].context&.dig(:kb_event)
+      return unless event
+
+      event[:retries] = event.fetch(:retries, 0) + 1
+      (event[:retry_errors] ||= []) << root_cause(error).class.name
+    end
+  end
+end

data/lib/kb/version.rb

@@ -1,3 +1,3 @@
 module KB
-  VERSION = '1.2.0'.freeze
+  VERSION = '1.4.0'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: barkibu-kb
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.4.0
 platform: ruby
 authors:
 - Léo Figea
@@ -247,6 +247,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: faraday-net_http_persistent
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.2'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.2'
 - !ruby/object:Gem::Dependency
   name: faraday_middleware
   requirement: !ruby/object:Gem::Requirement
@@ -261,6 +275,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: faraday-retry
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
 - !ruby/object:Gem::Dependency
   name: i18n
   requirement: !ruby/object:Gem::Requirement
@@ -275,6 +303,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: net-http-persistent
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '4.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '4.0'
 description: A wrapper of Barkibu's Knowledge Base Endpoint to make those entities
   and their respective CRUD operations available to a ruby app
 email:
@@ -311,6 +353,7 @@ files:
 - lib/kb/client_resolver.rb
 - lib/kb/concerns.rb
 - lib/kb/concerns/as_kb_wrapper.rb
+- lib/kb/connections.rb
 - lib/kb/errors.rb
 - lib/kb/errors/client_error.rb
 - lib/kb/errors/conflict_error.rb
@@ -352,6 +395,7 @@ files:
 - lib/kb/models/referral.rb
 - lib/kb/models/search_result.rb
 - lib/kb/models/symptom.rb
+- lib/kb/retry_policy.rb
 - lib/kb/type/array_of_conditions_type.rb
 - lib/kb/type/array_of_strings_type.rb
 - lib/kb/type/array_of_symptoms_type.rb