waterdrop 2.0.7 → 2.6.11

data/README.md

@@ -1,84 +1,40 @@
 # WaterDrop
 
-**Note**: Documentation presented here refers to WaterDrop `2.0.0`.
-
-WaterDrop `2.0` does **not** work with Karafka `1.*` and aims to either work as a standalone producer outside of Karafka `1.*` ecosystem or as a part of not yet released Karafka `2.0.*`.
-
-Please refer to [this](https://github.com/karafka/waterdrop/tree/1.4) branch and its documentation for details about WaterDrop `1.*` usage.
-
 [![Build Status](https://github.com/karafka/waterdrop/workflows/ci/badge.svg)](https://github.com/karafka/waterdrop/actions?query=workflow%3Aci)
 [![Gem Version](https://badge.fury.io/rb/waterdrop.svg)](http://badge.fury.io/rb/waterdrop)
 [![Join the chat at https://slack.karafka.io](https://raw.githubusercontent.com/karafka/misc/master/slack.svg)](https://slack.karafka.io)
 
-Gem used to send messages to Kafka in an easy way with an extra validation layer. It is a part of the [Karafka](https://github.com/karafka/karafka) ecosystem.
+WaterDrop is a standalone gem that sends messages to Kafka easily with an extra validation layer. It is a part of the [Karafka](https://github.com/karafka/karafka) ecosystem.
 
 It:
 
- - Is thread safe
+ - Is thread-safe
  - Supports sync producing
  - Supports async producing
+ - Supports transactions
  - Supports buffering
  - Supports producing messages to multiple clusters
  - Supports multiple delivery policies
- - Works with Kafka 1.0+ and Ruby 2.6+
-
-## Table of contents
+ - Works with Kafka `1.0+` and Ruby `2.7+`
+ - Works with and without Karafka
 
-- [Installation](#installation)
-- [Setup](#setup)
-  * [WaterDrop configuration options](#waterdrop-configuration-options)
-  * [Kafka configuration options](#kafka-configuration-options)
-- [Usage](#usage)
-  * [Basic usage](#basic-usage)
-  * [Buffering](#buffering)
-      + [Using WaterDrop to buffer messages based on the application logic](#using-waterdrop-to-buffer-messages-based-on-the-application-logic)
-      + [Using WaterDrop with rdkafka buffers to achieve periodic auto-flushing](#using-waterdrop-with-rdkafka-buffers-to-achieve-periodic-auto-flushing)
-- [Instrumentation](#instrumentation)
-  * [Usage statistics](#usage-statistics)
-  * [Error notifications](#error-notifications)
-  * [Forking and potential memory problems](#forking-and-potential-memory-problems)
-- [Note on contributions](#note-on-contributions)
-
-## Installation
-
-```ruby
-gem install waterdrop
-```
-
-or add this to your Gemfile:
-
-```ruby
-gem 'waterdrop'
-```
-
-and run
-
-```
-bundle install
-```
+## Documentation
 
-## Setup
+Karafka ecosystem components documentation, including WaterDrop, can be found [here](https://karafka.io/docs/#waterdrop).
 
-WaterDrop is a complex tool, that contains multiple configuration options. To keep everything organized, all the configuration options were divided into two groups:
+## Getting Started
 
-- WaterDrop options - options directly related to WaterDrop and its components
-- Kafka driver options - options related to `rdkafka`
+If you want to both produce and consume messages, please use [Karafka](https://github.com/karafka/karafka/). It integrates WaterDrop automatically.
 
-To apply all those configuration options, you need to create a producer instance and use the ```#setup``` method:
+To get started with WaterDrop:
 
-```ruby
-producer = WaterDrop::Producer.new
+1. Add it to your Gemfile:
 
-producer.setup do |config|
-  config.deliver = true
-  config.kafka = {
-    'bootstrap.servers': 'localhost:9092',
-    'request.required.acks': 1
-  }
-end
+```bash
+bundle add waterdrop
 ```
 
-or you can do the same while initializing the producer:
+2. Create and configure a producer:
 
 ```ruby
 producer = WaterDrop::Producer.new do |config|
@@ -90,41 +46,17 @@ producer = WaterDrop::Producer.new do |config|
 end
 ```
 
-### WaterDrop configuration options
+3. Use it as follows:
 
-| Option             | Description                                                     |
-|--------------------|-----------------------------------------------------------------|
-| `id`               | id of the producer for instrumentation and logging              |
-| `logger`           | Logger that we want to use                                      |
-| `deliver`          | Should we send messages to Kafka or just fake the delivery      |
-| `max_wait_timeout` | Waits that long for the delivery report or raises an error      |
-| `wait_timeout`     | Waits that long before re-check of delivery report availability |
-
-### Kafka configuration options
-
-You can create producers with different `kafka` settings. Documentation of the available configuration options is available on https://github.com/edenhill/librdkafka/blob/master/CONFIGURATION.md.
-
-## Usage
-
-Please refer to the [documentation](https://www.rubydoc.info/gems/waterdrop) in case you're interested in the more advanced API.
-
-### Basic usage
-
-To send Kafka messages, just create a producer and use it:
 
 ```ruby
-producer = WaterDrop::Producer.new
-
-producer.setup do |config|
-  config.kafka = { 'bootstrap.servers': 'localhost:9092' }
-end
-
+# sync producing
 producer.produce_sync(topic: 'my-topic', payload: 'my message')
 
 # or for async
 producer.produce_async(topic: 'my-topic', payload: 'my message')
 
-# or in batches
+# or in sync batches
 producer.produce_many_sync(
   [
     { topic: 'my-topic', payload: 'my message'},
@@ -132,7 +64,7 @@ producer.produce_many_sync(
   ]
 )
 
-# both sync and async
+# and async batches
 producer.produce_many_async(
   [
     { topic: 'my-topic', payload: 'my message'},
@@ -140,194 +72,9 @@ producer.produce_many_async(
   ]
 )
 
-# Don't forget to close the producer once you're done to flush the internal buffers, etc
-producer.close
-```
-
-Each message that you want to publish, will have its value checked.
-
-Here are all the things you can provide in the message hash:
-
-| Option          | Required | Value type    | Description                                              |
-|-----------------|----------|---------------|----------------------------------------------------------|
-| `topic`         | true     | String        | The Kafka topic that should be written to                |
-| `payload`       | true     | String        | Data you want to send to Kafka                           |
-| `key`           | false    | String        | The key that should be set in the Kafka message          |
-| `partition`     | false    | Integer       | A specific partition number that should be written to    |
-| `partition_key` | false    | String        | Key to indicate the destination partition of the message |
-| `timestamp`     | false    | Time, Integer | The timestamp that should be set on the message          |
-| `headers`       | false    | Hash          | Headers for the message                                  |
-
-Keep in mind, that message you want to send should be either binary or stringified (to_s, to_json, etc).
-
-### Buffering
-
-WaterDrop producers support buffering messages in their internal buffers and on the `rdkafka` level via `queue.buffering.*` set of settings.
-
-This means that depending on your use case, you can achieve both granular buffering and flushing control when needed with context awareness and periodic and size-based flushing functionalities.
-
-#### Using WaterDrop to buffer messages based on the application logic
-
-```ruby
-producer = WaterDrop::Producer.new
-
-producer.setup do |config|
-  config.kafka = { 'bootstrap.servers': 'localhost:9092' }
-end
-
-# Simulating some events states of a transaction - notice, that the messages will be flushed to
-# kafka only upon arrival of the `finished` state.
-%w[
-  started
-  processed
-  finished
-].each do |state|
-  producer.buffer(topic: 'events', payload: state)
-
-  puts "The messages buffer size #{producer.messages.size}"
-  producer.flush_sync if state == 'finished'
-  puts "The messages buffer size #{producer.messages.size}"
-end
-
-producer.close
-```
-
-#### Using WaterDrop with rdkafka buffers to achieve periodic auto-flushing
-
-```ruby
-producer = WaterDrop::Producer.new
-
-producer.setup do |config|
-  config.kafka = {
-    'bootstrap.servers': 'localhost:9092',
-    # Accumulate messages for at most 10 seconds
-    'queue.buffering.max.ms' => 10_000
-  }
-end
-
-# WaterDrop will flush messages minimum once every 10 seconds
-30.times do |i|
-  producer.produce_async(topic: 'events', payload: i.to_s)
-  sleep(1)
-end
-
-producer.close
-```
-
-## Instrumentation
-
-Each of the producers after the `#setup` is done, has a custom monitor to which you can subscribe.
-
-```ruby
-producer = WaterDrop::Producer.new
-
-producer.setup do |config|
-  config.kafka = { 'bootstrap.servers': 'localhost:9092' }
-end
-
-producer.monitor.subscribe('message.produced_async') do |event|
-  puts "A message was produced to '#{event[:message][:topic]}' topic!"
-end
-
-producer.produce_async(topic: 'events', payload: 'data')
-
-producer.close
-```
-
-See the `WaterDrop::Instrumentation::Monitor::EVENTS` for the list of all the supported events.
-
-### Usage statistics
-
-WaterDrop may be configured to emit internal metrics at a fixed interval by setting the `kafka` `statistics.interval.ms` configuration property to a value > `0`. Once that is done, emitted statistics are available after subscribing to the `statistics.emitted` publisher event.
-
-The statistics include all of the metrics from `librdkafka` (full list [here](https://github.com/edenhill/librdkafka/blob/master/STATISTICS.md)) as well as the diff of those against the previously emitted values.
-
-For several attributes like `txmsgs`, `librdkafka` publishes only the totals. In order to make it easier to track the progress (for example number of messages sent between statistics emitted events), WaterDrop diffs all the numeric values against previously available numbers. All of those metrics are available under the same key as the metric but with additional `_d` postfix:
-
-
-```ruby
-producer = WaterDrop::Producer.new do |config|
-  config.kafka = {
-    'bootstrap.servers': 'localhost:9092',
-    'statistics.interval.ms': 2_000 # emit statistics every 2 seconds
-  }
-end
-
-producer.monitor.subscribe('statistics.emitted') do |event|
-  sum = event[:statistics]['txmsgs']
-  diff = event[:statistics]['txmsgs_d']
-
-  p "Sent messages: #{sum}"
-  p "Messages sent from last statistics report: #{diff}"
-end
-
-sleep(2)
-
-# Sent messages: 0
-# Messages sent from last statistics report: 0
-
-20.times { producer.produce_async(topic: 'events', payload: 'data') }
-
-# Sent messages: 20
-# Messages sent from last statistics report: 20
-
-sleep(2)
-
-20.times { producer.produce_async(topic: 'events', payload: 'data') }
-
-# Sent messages: 40
-# Messages sent from last statistics report: 20
-
-sleep(2)
-
-# Sent messages: 40
-# Messages sent from last statistics report: 0
-
-producer.close
-```
-
-Note: The metrics returned may not be completely consistent between brokers, toppars and totals, due to the internal asynchronous nature of librdkafka. E.g., the top level tx total may be less than the sum of the broker tx values which it represents.
-
-### Error notifications
-
-Aside from errors related to publishing messages like `buffer.flushed_async.error`, WaterDrop allows you to listen to errors that occur in its internal background threads. Things like reconnecting to Kafka upon network errors and others unrelated to publishing messages are all available under `error.emitted` notification key. You can subscribe to this event to ensure your setup is healthy and without any problems that would otherwise go unnoticed as long as messages are delivered.
-
-```ruby
-producer = WaterDrop::Producer.new do |config|
-  # Note invalid connection port...
-  config.kafka = { 'bootstrap.servers': 'localhost:9090' }
-end
-
-producer.monitor.subscribe('error.emitted') do |event|
-  error = event[:error]
-
-  p "Internal error occurred: #{error}"
+# transactions
+producer.transaction do
+  producer.produce_async(topic: 'my-topic', payload: 'my message')
+  producer.produce_async(topic: 'my-topic', payload: 'my message')
 end
-
-# Run this code without Kafka cluster
-loop do
-  producer.produce_async(topic: 'events', payload: 'data')
-
-  sleep(1)
-end
-
-# After you stop your Kafka cluster, you will see a lot of those:
-#
-# Internal error occurred: Local: Broker transport failure (transport)
-#
-# Internal error occurred: Local: Broker transport failure (transport)
 ```
-
-### Forking and potential memory problems
-
-If you work with forked processes, make sure you **don't** use the producer before the fork. You can easily configure the producer and then fork and use it.
-
-To tackle this [obstacle](https://github.com/appsignal/rdkafka-ruby/issues/15) related to rdkafka, WaterDrop adds finalizer to each of the producers to close the rdkafka client before the Ruby process is shutdown. Due to the [nature of the finalizers](https://www.mikeperham.com/2010/02/24/the-trouble-with-ruby-finalizers/), this implementation prevents producers from being GCed (except upon VM shutdown) and can cause memory leaks if you don't use persistent/long-lived producers in a long-running process or if you don't use the `#close` method of a producer when it is no longer needed. Creating a producer instance for each message is anyhow a rather bad idea, so we recommend not to.
-
-## Note on contributions
-
-First, thank you for considering contributing to the Karafka ecosystem! It's people like you that make the open source community such a great community!
-
-Each pull request must pass all the RSpec specs, integration tests and meet our quality requirements.
-
-Fork it, update and wait for the Github Actions results.

data/certs/cert_chain.pem

@@ -0,0 +1,26 @@
+-----BEGIN CERTIFICATE-----
+MIIEcDCCAtigAwIBAgIBATANBgkqhkiG9w0BAQsFADA/MRAwDgYDVQQDDAdjb250
+YWN0MRcwFQYKCZImiZPyLGQBGRYHa2FyYWZrYTESMBAGCgmSJomT8ixkARkWAmlv
+MB4XDTIzMDgyMTA3MjU1NFoXDTI0MDgyMDA3MjU1NFowPzEQMA4GA1UEAwwHY29u
+dGFjdDEXMBUGCgmSJomT8ixkARkWB2thcmFma2ExEjAQBgoJkiaJk/IsZAEZFgJp
+bzCCAaIwDQYJKoZIhvcNAQEBBQADggGPADCCAYoCggGBAOuZpyQKEwsTG9plLat7
+8bUaNuNBEnouTsNMr6X+XTgvyrAxTuocdsyP1sNCjdS1B8RiiDH1/Nt9qpvlBWon
+sdJ1SYhaWNVfqiYStTDnCx3PRMmHRdD4KqUWKpN6VpZ1O/Zu+9Mw0COmvXgZuuO9
+wMSJkXRo6dTCfMedLAIxjMeBIxtoLR2e6Jm6MR8+8WYYVWrO9kSOOt5eKQLBY7aK
+b/Dc40EcJKPg3Z30Pia1M9ZyRlb6SOj6SKpHRqc7vbVQxjEw6Jjal1lZ49m3YZMd
+ArMAs9lQZNdSw5/UX6HWWURLowg6k10RnhTUtYyzO9BFev0JFJftHnmuk8vtb+SD
+5VPmjFXg2VOcw0B7FtG75Vackk8QKfgVe3nSPhVpew2CSPlbJzH80wChbr19+e3+
+YGr1tOiaJrL6c+PNmb0F31NXMKpj/r+n15HwlTMRxQrzFcgjBlxf2XFGnPQXHhBm
+kp1OFnEq4GG9sON4glRldkwzi/f/fGcZmo5fm3d+0ZdNgwIDAQABo3cwdTAJBgNV
+HRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHQ4EFgQUPVH5+dLA80A1kJ2Uz5iGwfOa
+1+swHQYDVR0RBBYwFIESY29udGFjdEBrYXJhZmthLmlvMB0GA1UdEgQWMBSBEmNv
+bnRhY3RAa2FyYWZrYS5pbzANBgkqhkiG9w0BAQsFAAOCAYEAnpa0jcN7JzREHMTQ
+bfZ+xcvlrzuROMY6A3zIZmQgbnoZZNuX4cMRrT1p1HuwXpxdpHPw7dDjYqWw3+1h
+3mXLeMuk7amjQpYoSWU/OIZMhIsARra22UN8qkkUlUj3AwTaChVKN/bPJOM2DzfU
+kz9vUgLeYYFfQbZqeI6SsM7ltilRV4W8D9yNUQQvOxCFxtLOetJ00fC/E7zMUzbK
+IBwYFQYsbI6XQzgAIPW6nGSYKgRhkfpmquXSNKZRIQ4V6bFrufa+DzD0bt2ZA3ah
+fMmJguyb5L2Gf1zpDXzFSPMG7YQFLzwYz1zZZvOU7/UCpQsHpID/YxqDp4+Dgb+Y
+qma0whX8UG/gXFV2pYWpYOfpatvahwi+A1TwPQsuZwkkhi1OyF1At3RY+hjSXyav
+AnG1dJU+yL2BK7vaVytLTstJME5mepSZ46qqIJXMuWob/YPDmVaBF39TDSG9e34s
+msG3BiCqgOgHAnL23+CN3Rt8MsuRfEtoTKpJVcCfoEoNHOkc
+-----END CERTIFICATE-----

data/config/locales/errors.yml

@@ -0,0 +1,33 @@
+en:
+  validations:
+    config:
+      missing: must be present
+      logger_format: must be present
+      deliver_format: must be boolean
+      id_format: must be a non-empty string
+      max_payload_size_format: must be an integer that is equal or bigger than 1
+      wait_timeout_format: must be a numeric that is bigger than 0
+      max_wait_timeout_format: must be an integer that is equal or bigger than 0
+      kafka_format: must be a hash with symbol based keys
+      kafka_key_must_be_a_symbol: All keys under the kafka settings scope need to be symbols
+      wait_on_queue_full_format: must be boolean
+      wait_backoff_on_queue_full_format: must be a numeric that is bigger or equal to 0
+      wait_timeout_on_queue_full_format: must be a numeric that is bigger or equal to 0
+
+    message:
+      missing: must be present
+      partition_format: must be an integer greater or equal to -1
+      topic_format: 'does not match the topic allowed format'
+      partition_key_format: must be a non-empty string
+      timestamp_format: must be either time or integer
+      payload_format: must be string or nil
+      headers_format: must be a hash
+      key_format: must be a non-empty string
+      payload_max_size: is more than `max_payload_size` config value
+      headers_invalid_key_type: all headers keys need to be of type String
+      headers_invalid_value_type: all headers values need to be of type String
+
+    test:
+      missing: must be present
+      nested.id_format: 'is invalid'
+      nested.id2_format: 'is invalid'

data/docker-compose.yml

@@ -1,18 +1,25 @@
 version: '2'
+
 services:
-  zookeeper:
-    image: wurstmeister/zookeeper
-    ports:
-      - "2181:2181"
   kafka:
-    image: wurstmeister/kafka:2.12-2.5.0
+    container_name: kafka
+    image: confluentinc/cp-kafka:7.5.1
+
     ports:
-      - "9092:9092"
+      - 9092:9092
+
     environment:
-      KAFKA_ADVERTISED_HOST_NAME: localhost
-      KAFKA_ADVERTISED_PORT: 9092
-      KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
+      CLUSTER_ID: kafka-docker-cluster-1
+      KAFKA_INTER_BROKER_LISTENER_NAME: PLAINTEXT
+      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
+      KAFKA_PROCESS_ROLES: broker,controller
+      KAFKA_CONTROLLER_LISTENER_NAMES: CONTROLLER
+      KAFKA_LISTENERS: PLAINTEXT://:9092,CONTROLLER://:9093
+      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT
+      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://127.0.0.1:9092
+      KAFKA_BROKER_ID: 1
+      KAFKA_CONTROLLER_QUORUM_VOTERS: 1@127.0.0.1:9093
+      ALLOW_PLAINTEXT_LISTENER: 'yes'
       KAFKA_AUTO_CREATE_TOPICS_ENABLE: 'true'
-      KAFKA_CREATE_TOPICS: 'example_topic:1:1'
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock
+      KAFKA_TRANSACTION_STATE_LOG_REPLICATION_FACTOR: 1
+      KAFKA_TRANSACTION_STATE_LOG_MIN_ISR: 1

data/lib/waterdrop/clients/buffered.rb

@@ -0,0 +1,90 @@
+# frozen_string_literal: true
+
+module WaterDrop
+  module Clients
+    # Client used to buffer messages that we send out in specs and other places.
+    class Buffered < Clients::Dummy
+      attr_accessor :messages
+
+      # @param args [Object] anything accepted by `Clients::Dummy`
+      def initialize(*args)
+        super
+        @messages = []
+        @topics = Hash.new { |k, v| k[v] = [] }
+
+        @transaction_active = false
+        @transaction_messages = []
+        @transaction_topics = Hash.new { |k, v| k[v] = [] }
+        @transaction_level = 0
+      end
+
+      # "Produces" message to Kafka: it acknowledges it locally, adds it to the internal buffer
+      # @param message [Hash] `WaterDrop::Producer#produce_sync` message hash
+      # @return [Dummy::Handle] fake delivery handle that can be materialized into a report
+      def produce(message)
+        if @transaction_active
+          @transaction_topics[message.fetch(:topic)] << message
+          @transaction_messages << message
+        else
+          # We pre-validate the message payload, so topic is ensured to be present
+          @topics[message.fetch(:topic)] << message
+          @messages << message
+        end
+
+        super(**message.to_h)
+      end
+
+      # Starts the transaction on a given level
+      def begin_transaction
+        @transaction_level += 1
+        @transaction_active = true
+      end
+
+      # Finishes given level of transaction
+      def commit_transaction
+        @transaction_level -= 1
+
+        return unless @transaction_level.zero?
+
+        # Transfer transactional data on success
+        @transaction_topics.each do |topic, messages|
+          @topics[topic] += messages
+        end
+
+        @messages += @transaction_messages
+
+        @transaction_topics.clear
+        @transaction_messages.clear
+        @transaction_active = false
+      end
+
+      # Aborts the transaction
+      def abort_transaction
+        @transaction_level -= 1
+
+        return unless @transaction_level.zero?
+
+        @transaction_topics.clear
+        @transaction_messages.clear
+        @transaction_active = false
+      end
+
+      # Returns messages produced to a given topic
+      # @param topic [String]
+      def messages_for(topic)
+        @topics[topic]
+      end
+
+      # Clears internal buffer
+      # Used in between specs so messages do not leak out
+      def reset
+        @transaction_level = 0
+        @transaction_active = false
+        @transaction_topics.clear
+        @transaction_messages.clear
+        @messages.clear
+        @topics.each_value(&:clear)
+      end
+    end
+  end
+end

data/lib/waterdrop/clients/dummy.rb

@@ -0,0 +1,69 @@
+# frozen_string_literal: true
+
+module WaterDrop
+  module Clients
+    # A dummy client that is supposed to be used instead of Rdkafka::Producer in case we don't
+    # want to dispatch anything to Kafka.
+    #
+    # It does not store anything and just ignores messages. It does however return proper delivery
+    # handle that can be materialized into a report.
+    class Dummy
+      # `::Rdkafka::Producer::DeliveryHandle` object API compatible dummy object
+      class Handle < ::Rdkafka::Producer::DeliveryHandle
+        # @param topic [String] topic where we want to dispatch message
+        # @param partition [Integer] target partition
+        # @param offset [Integer] offset assigned by our fake "Kafka"
+        def initialize(topic, partition, offset)
+          @topic = topic
+          @partition = partition
+          @offset = offset
+        end
+
+        # Does not wait, just creates the result
+        #
+        # @param _args [Array] anything the wait handle would accept
+        # @return [::Rdkafka::Producer::DeliveryReport]
+        def wait(*_args)
+          create_result
+        end
+
+        # Creates a delivery report with details where the message went
+        #
+        # @return [::Rdkafka::Producer::DeliveryReport]
+        def create_result
+          ::Rdkafka::Producer::DeliveryReport.new(
+            @partition,
+            @offset,
+            @topic
+          )
+        end
+      end
+
+      # @param _producer [WaterDrop::Producer]
+      # @return [Dummy] dummy instance
+      def initialize(_producer)
+        @counters = Hash.new { |h, k| h[k] = -1 }
+      end
+
+      # "Produces" the message
+      # @param topic [String, Symbol] topic where we want to dispatch message
+      # @param partition [Integer] target partition
+      # @param _args [Hash] remaining details that are ignored in the dummy mode
+      # @return [Handle] delivery handle
+      def produce(topic:, partition: 0, **_args)
+        Handle.new(topic.to_s, partition, @counters["#{topic}#{partition}"] += 1)
+      end
+
+      # @param _args [Object] anything really, this dummy is suppose to support anything
+      def respond_to_missing?(*_args)
+        true
+      end
+
+      # @param _args [Object] anything really, this dummy is suppose to support anything
+      # @return [self] returns self for chaining cases
+      def method_missing(*_args)
+        self || super
+      end
+    end
+  end
+end

data/lib/waterdrop/clients/rdkafka.rb

@@ -0,0 +1,34 @@
+# frozen_string_literal: true
+
+module WaterDrop
+  # Namespace for all the clients that WaterDrop may use under the hood
+  module Clients
+    # Default Rdkafka client.
+    # Since we use the ::Rdkafka::Producer under the hood, this is just a module that aligns with
+    # client building API for the convenience.
+    module Rdkafka
+      class << self
+        # @param producer [WaterDrop::Producer] producer instance with its config, etc
+        # @note We overwrite this that way, because we do not care
+        def new(producer)
+          config = producer.config.kafka.to_h
+
+          client = ::Rdkafka::Config.new(config).producer
+
+          # This callback is not global and is per client, thus we do not have to wrap it with a
+          # callbacks manager to make it work
+          client.delivery_callback = Instrumentation::Callbacks::Delivery.new(
+            producer.id,
+            producer.transactional?,
+            producer.config.monitor
+          )
+
+          # Switch to the transactional mode if user provided the transactional id
+          client.init_transactions if config.key?(:'transactional.id')
+
+          client
+        end
+      end
+    end
+  end
+end