karafka 1.0.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 49921e358054ab6470899c0e122cc9c93f5398ea
-  data.tar.gz: 183d5ff52e6f4ce09110287147d735929ff2a6e7
+SHA256:
+  metadata.gz: 0bb0a1f72768ebf4bf720ebda57ebc26a0178275adabffd494b24e1612e9b38a
+  data.tar.gz: f586038a0498227e8a287cc173a23e77bb99b6cb8d453c39be55a220e2a0d361
 SHA512:
-  metadata.gz: cd8ad63256d3133dbc1c4a4676b54c64815353047a8cb42c87e6ef343ff6af12099ff07d03d01b4a3b61fc648d79dc6b13c1f969a48f3ab04f1dc3a91799e99b
-  data.tar.gz: 345addc070e2b13fc7d11f07faefccbcfbffeedad3ce106d98a335c0e54f5c29731fc9288c46b114aee4df62f7578c2e120e8b61b7a378c517881221b2254e4e
+  metadata.gz: e2b862da6372bc91f76bc01c20eb21ccde9d61d67749ccce97eadd2f739484dbd68a149d08d6e275d94d95b6ce9610d86c2d01e85bb1841a80e048ed832810ac
+  data.tar.gz: 06fb89700e59f810ec984b54f0424cfdeb98c79e17b8629010f011e68edff5fa1e345576a7b28ed07aff440739ed11824016da6083601a92b8f83fcca68e576e

data/.ruby-version

@@ -1 +1 @@
-2.4.1
+2.5.0

data/.travis.yml

@@ -8,7 +8,9 @@ rvm:
   - 2.3.4
   - 2.4.0
   - 2.4.1
-  - jruby-9.1.12.0
+  - 2.4.2
+  - 2.5.0
+  - jruby-head
 script: bundle exec rspec spec/
 env:
   global:

data/CHANGELOG.md

@@ -1,5 +1,92 @@
 # Karafka framework changelog
 
+## 1.2.0
+- Spec improvements
+- #260 - Specs missing randomization
+- #251 - Shutdown upon non responding (unreachable) cluster is not possible
+- #258 - Investigate lowering requirements on activesupport
+- #246 - Alias consumer#mark_as_consumed on controller
+- #259 - Allow forcing key/partition key on responders
+- #267 - Styling inconsistency
+- #242 - Support setting the max bytes to fetch per request
+- #247 - Support SCRAM once released
+- #271 - Provide an after_init option to pass a configuration block
+- #262 - Error in the monitor code for NewRelic
+- #241 - Performance metrics
+- #274 - Rename controllers to consumers
+- #184 - Seek to
+- #284 - Dynamic Params parent class
+- #275 - ssl_ca_certs_from_system
+- #296 - Instrument forceful exit with an error
+- Replaced some of the activesupport parts with dry-inflector
+- Lower ActiveSupport dependency
+- Remove configurators in favor of the after_init block configurator
+- Ruby 2.5.0 support
+- Renamed Karafka::Connection::Processor to Karafka::Connection::Delegator to match incoming naming conventions
+- Renamed Karafka::Connection::Consumer to Karafka::Connection::Client due to #274
+- Removed HashWithIndifferentAccess in favor of a regular hash
+- JSON parsing defaults now to string keys
+- Lower memory usage due to less params data internal details
+- Support multiple ```after_init``` blocks in favor of a single one
+- Renamed ```received_at``` to ```receive_time``` to follow ruby-kafka and WaterDrop conventions
+- Adjust internal setup to easier map Ruby-Kafka config changes
+- System callbacks reorganization
+- Added ```before_fetch_loop``` configuration block for early client usage (```#seek```, etc)
+- Renamed ```after_fetched``` to ```after_fetch``` to normalize the naming convention
+- Instrumentation on a connection delegator level
+- Added ```params_batch#last``` method to retrieve last element after unparsing
+- All params keys are now strings
+
+## 1.1.2
+- #256 - Default kafka.seed_brokers configuration is created in invalid format
+
+## 1.1.1
+- #253 - Allow providing a global per app parser in config settings
+
+## 1.1.0
+- Gem bump
+- Switch from Celluloid to native Thread management
+- Improved shutdown process
+- Introduced optional fetch callbacks and moved current the ```after_received``` there as well
+- Karafka will raise Errors::InvalidPauseTimeout exception when trying to pause but timeout set to 0
+- Allow float for timeouts and other time based second settings
+- Renamed MessagesProcessor to Processor and MessagesConsumer to Consumer - we don't process and don't consumer anything else so it was pointless to keep this "namespace"
+- #232 - Remove unused ActiveSupport require
+- #214 - Expose consumer on a controller layer
+- #193 - Process shutdown callbacks
+- Fixed accessibility of ```#params_batch``` from the outside of the controller
+- connection_pool config options are no longer required
+- celluloid config options are no longer required
+- ```#perform``` is now renamed to ```#consume``` with warning level on using the old one (deprecated)
+- #235 - Rename perform to consume
+- Upgrade to ruby-kafka 0.5
+- Due to redesign of Waterdrop concurrency setting is no longer needed
+- #236 - Manual offset management
+- WaterDrop 1.0.0 support with async
+- Renamed ```batch_consuming``` option to ```batch_fetching``` as it is not a consumption (with processing) but a process of fetching messages from Kafka. The messages is considered consumed, when it is processed.
+- Renamed ```batch_processing``` to ```batch_consuming``` to resemble Kafka concept of consuming messages.
+- Renamed ```after_received``` to ```after_fetched``` to normalize the naming conventions.
+- Responders support the per topic ```async``` option.
+
+## 1.0.1
+- #210 - LoadError: cannot load such file -- [...]/karafka.rb
+- Ruby 2.4.2 as a default (+travis integration)
+- JRuby upgrade
+- Expanded persistence layer (moved to a namespace for easier future development)
+- #213 - Misleading error when non-existing dependency is required
+- #212 - Make params react to #topic, #partition, #offset
+- #215 - Consumer group route dynamic options are ignored
+- #217 - check RUBY_ENGINE constant if RUBY_VERSION is missing (#217)
+- #218 - add configuration setting to control Celluloid's shutdown timeout
+- Renamed Karafka::Routing::Mapper to Karafka::Routing::TopicMapper to match naming conventions
+- #219 - Allow explicit consumer group names, without prefixes
+- Fix to early removed pid upon shutdown of demonized process
+- max_wait_time updated to match https://github.com/zendesk/ruby-kafka/issues/433
+- #230 - Better uri validation for seed brokers (incompatibility as the kafka:// or kafka+ssl:// is required)
+- Small internal docs fixes
+- Dry::Validation::MissingMessageError: message for broker_schema? was not found
+- #238 - warning: already initialized constant Karafka::Schemas::URI_SCHEMES
+
 ## 1.0.0
 
 ### Closed issues:
@@ -41,11 +128,11 @@
 
 ### New features and improvements
 
-- batch processing thanks to ```#batch_processing``` flag and ```#params_batch``` on controllers
+- batch processing thanks to ```#batch_consuming``` flag and ```#params_batch``` on controllers
 - ```#topic``` method on an controller instance to make a clear distinction in between params and route details
 - Changed routing model (still compatible with 0.5) to allow better resources management
 - Lower memory requirements due to object creation limitation (2-3 times less objects on each new message)
-- Introduced the ```#batch_processing``` config flag (config for #126) that can be set per each consumer_group
+- Introduced the ```#batch_consuming``` config flag (config for #126) that can be set per each consumer_group
 - Added support for partition, offset and partition key in the params hash
 - ```name``` option in config renamed to ```client_id```
 - Long running controllers with ```persistent``` flag on a topic config level, to make controller instances persistent between messages batches (single controller instance per topic per partition no per messages batch) - turned on by default
@@ -58,7 +145,7 @@
 - ```start_from_beginning``` moved into kafka scope (```kafka.start_from_beginning```)
 - Router no longer checks for route uniqueness - now you can define same routes for multiple kafkas and do a lot of crazy stuff, so it's your responsibility to check uniqueness
 - Change in the way we identify topics in between Karafka and Sidekiq workers. If you upgrade, please make sure, all the jobs scheduled in Sidekiq are finished before the upgrade.
-- ```batch_mode``` renamed to ```batch_consuming```
+- ```batch_mode``` renamed to ```batch_fetching```
 - Renamed content to value to better resemble ruby-kafka internal messages naming convention
 - When having a responder with ```required``` topics and not using ```#respond_with``` at all, it will raise an exception
 - Renamed ```inline_mode``` to ```inline_processing``` to resemble other settings conventions

data/CONTRIBUTING.md

@@ -9,7 +9,6 @@ We welcome any type of contribution, not only code. You can help with
 - **Marketing**: writing blog posts, howto's, printing stickers, ...
 - **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ...
 - **Code**: take a look at the [open issues](issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them.
-- **Money**: we welcome financial contributions in full transparency on our [open collective](https://opencollective.com/karafka).
 
 ## Your First Contribution
 
@@ -21,13 +20,13 @@ Any code change should be submitted as a pull request. The description should ex
 
 ## Code review process
 
-The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge.
-It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you?
+Each pull request must pass all the rspec specs and meet our quality requirements.
 
-## Financial contributions
+To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combines multiple linters and code analyzers for both code and documentation. Once you're done with your changes, submit a pull request.
 
-We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/karafka).
-Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.
+Coditsu will automatically check your work against our quality standards. You can find your commit check results on the [builds page](https://app.coditsu.io/karafka/commit_builds) of Karafka organization.
+
+[![coditsu](https://coditsu.io/assets/quality_bar.svg)](https://app.coditsu.io/karafka/commit_builds)
 
 ## Questions
 

data/Gemfile

@@ -5,7 +5,7 @@ source 'https://rubygems.org'
 gemspec
 
 group :development, :test do
-  gem 'timecop'
   gem 'rspec'
   gem 'simplecov'
+  gem 'timecop'
 end

data/Gemfile.lock

@@ -1,119 +1,114 @@
 PATH
   remote: .
   specs:
-    karafka (1.0.0)
-      activesupport (>= 5.0)
-      celluloid
+    karafka (1.2.0)
+      activesupport (>= 4.0)
       dry-configurable (~> 0.7)
+      dry-inflector (~> 0.1.1)
+      dry-monitor (~> 0.1)
       dry-validation (~> 0.11)
       envlogic (~> 1.0)
       multi_json (>= 1.12)
       rake (>= 11.3)
       require_all (>= 1.4)
-      ruby-kafka (>= 0.4)
+      ruby-kafka (>= 0.5.3)
       thor (~> 0.19)
-      waterdrop (>= 0.4)
+      waterdrop (~> 1.2)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (5.1.3)
+    activesupport (5.1.5)
       concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (~> 0.7)
       minitest (~> 5.1)
       tzinfo (~> 1.1)
-    celluloid (0.17.3)
-      celluloid-essentials
-      celluloid-extras
-      celluloid-fsm
-      celluloid-pool
-      celluloid-supervision
-      timers (>= 4.1.1)
-    celluloid-essentials (0.20.5)
-      timers (>= 4.1.1)
-    celluloid-extras (0.20.5)
-      timers (>= 4.1.1)
-    celluloid-fsm (0.20.5)
-      timers (>= 4.1.1)
-    celluloid-pool (0.20.5)
-      timers (>= 4.1.1)
-    celluloid-supervision (0.20.6)
-      timers (>= 4.1.1)
     concurrent-ruby (1.0.5)
-    connection_pool (2.2.1)
+    delivery_boy (0.2.4)
+      king_konf (~> 0.1.8)
+      ruby-kafka (~> 0.5.1)
     diff-lcs (1.3)
-    docile (1.1.5)
+    docile (1.3.0)
     dry-configurable (0.7.0)
       concurrent-ruby (~> 1.0)
     dry-container (0.6.0)
       concurrent-ruby (~> 1.0)
       dry-configurable (~> 0.1, >= 0.1.3)
-    dry-core (0.3.3)
+    dry-core (0.4.5)
       concurrent-ruby (~> 1.0)
     dry-equalizer (0.2.0)
-    dry-logic (0.4.1)
+    dry-events (0.1.0)
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 0.4)
+      dry-equalizer (~> 0.2)
+    dry-inflector (0.1.1)
+    dry-logic (0.4.2)
       dry-container (~> 0.2, >= 0.2.6)
       dry-core (~> 0.2)
       dry-equalizer (~> 0.2)
-    dry-types (0.11.1)
+    dry-monitor (0.1.2)
+      dry-configurable (~> 0.5)
+      dry-equalizer (~> 0.2)
+      dry-events (~> 0.1)
+      rouge (~> 2.0, >= 2.2.1)
+    dry-types (0.12.2)
       concurrent-ruby (~> 1.0)
       dry-configurable (~> 0.1)
       dry-container (~> 0.3)
       dry-core (~> 0.2, >= 0.2.1)
       dry-equalizer (~> 0.2)
-      dry-logic (~> 0.4, >= 0.4.0)
+      dry-logic (~> 0.4, >= 0.4.2)
       inflecto (~> 0.0.0, >= 0.0.2)
-    dry-validation (0.11.0)
+    dry-validation (0.11.1)
       concurrent-ruby (~> 1.0)
       dry-configurable (~> 0.1, >= 0.1.3)
       dry-core (~> 0.2, >= 0.2.1)
       dry-equalizer (~> 0.2)
       dry-logic (~> 0.4, >= 0.4.0)
-      dry-types (~> 0.11.0)
-    envlogic (1.0.4)
-      activesupport
-    hitimes (1.2.6)
-    i18n (0.8.6)
+      dry-types (~> 0.12.0)
+    envlogic (1.1.0)
+      dry-inflector (~> 0.1)
+    i18n (0.9.5)
+      concurrent-ruby (~> 1.0)
     inflecto (0.0.2)
     json (2.1.0)
-    minitest (5.10.3)
-    multi_json (1.12.2)
-    null-logger (0.1.4)
-    rake (12.0.0)
-    require_all (1.4.0)
-    rspec (3.6.0)
-      rspec-core (~> 3.6.0)
-      rspec-expectations (~> 3.6.0)
-      rspec-mocks (~> 3.6.0)
-    rspec-core (3.6.0)
-      rspec-support (~> 3.6.0)
-    rspec-expectations (3.6.0)
+    king_konf (0.1.10)
+    minitest (5.11.3)
+    multi_json (1.13.1)
+    null-logger (0.1.5)
+    rake (12.3.1)
+    require_all (2.0.0)
+    rouge (2.2.1)
+    rspec (3.7.0)
+      rspec-core (~> 3.7.0)
+      rspec-expectations (~> 3.7.0)
+      rspec-mocks (~> 3.7.0)
+    rspec-core (3.7.1)
+      rspec-support (~> 3.7.0)
+    rspec-expectations (3.7.0)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.6.0)
-    rspec-mocks (3.6.0)
+      rspec-support (~> 3.7.0)
+    rspec-mocks (3.7.0)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.6.0)
-    rspec-support (3.6.0)
-    ruby-kafka (0.4.1)
-    simplecov (0.15.0)
-      docile (~> 1.1.0)
+      rspec-support (~> 3.7.0)
+    rspec-support (3.7.1)
+    ruby-kafka (0.5.4)
+    simplecov (0.16.1)
+      docile (~> 1.1)
       json (>= 1.8, < 3)
       simplecov-html (~> 0.10.0)
     simplecov-html (0.10.2)
     thor (0.20.0)
     thread_safe (0.3.6)
     timecop (0.9.1)
-    timers (4.1.2)
-      hitimes
-    tzinfo (1.2.3)
+    tzinfo (1.2.5)
       thread_safe (~> 0.1)
-    waterdrop (0.4.0)
-      bundler
-      connection_pool
-      dry-configurable (~> 0.6)
+    waterdrop (1.2.0)
+      delivery_boy (~> 0.2)
+      dry-configurable (~> 0.7)
+      dry-monitor (~> 0.1)
+      dry-validation (~> 0.11)
       null-logger
-      rake
-      ruby-kafka (~> 0.4)
 
 PLATFORMS
   ruby
@@ -125,4 +120,4 @@ DEPENDENCIES
   timecop
 
 BUNDLED WITH
-   1.14.6
+   1.16.1

data/README.md

@@ -1,17 +1,26 @@
 ![karafka logo](https://raw.githubusercontent.com/karafka/misc/master/logo/karafka_logotype_transparent2.png)
 
-[![Build Status](https://travis-ci.org/karafka/karafka.png)](https://travis-ci.org/karafka/karafka)
-[![Backers on Open Collective](https://opencollective.com/karafka/backers/badge.svg)](#backers) [![Sponsors on Open Collective](https://opencollective.com/karafka/sponsors/badge.svg)](#sponsors) [![Join the chat at https://gitter.im/karafka/karafka](https://badges.gitter.im/karafka/karafka.svg)](https://gitter.im/karafka/karafka?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![Build Status](https://travis-ci.org/karafka/karafka.svg?branch=master)](https://travis-ci.org/karafka/karafka)
 
 Framework used to simplify Apache Kafka based Ruby applications development.
 
-It allows programmers to use approach similar to standard HTTP conventions (```params``` and ```params_batch```) when working with asynchronous Kafka messages.
+Karafka allows you to capture everything that happens in your systems in large scale, providing you with a seamless and stable core for consuming and processing this data, without having to focus on things that are not your business domain.
 
 Karafka not only handles incoming messages but also provides tools for building complex data-flow applications that receive and send messages.
 
+**Warning**: Wiki and all the docs refer to the 1.2.0.beta4. Sorry for the inconvenience. We will release the stable 1.2.0 version soon.
+
 ## How does it work
 
-Karafka provides a higher-level abstraction that allows you to focus on your business logic development, instead of focusing on  implementing lower level abstration layers. It provides developers with a set of tools that are dedicated for building multi-topic applications similarly to how Rails applications are being built.
+Karafka provides a higher-level abstraction that allows you to focus on your business logic development, instead of focusing on implementing lower level abstraction layers. It provides developers with a set of tools that are dedicated for building multi-topic applications similarly to how Rails applications are being built.
+
+### Some things you might wonder about:
+
+- You can integrate Karafka with **any** Ruby based application.
+- Karafka does **not** require Sidekiq or any other third party software (apart from Kafka itself).
+- Karafka works with Ruby on Rails but it is a **standalone** framework that can work without it.
+- Karafka has a **minimal** set of dependencies, so adding it won't be a huge burden for your already existing applications.
+- Karafka processes can be executed for a **given subset** of consumer groups and/or topics, so you can fine tune it depending on your business logic.
 
 Karafka based applications can be easily deployed to any type of infrastructure, including those based on:
 
@@ -19,6 +28,12 @@ Karafka based applications can be easily deployed to any type of infrastructure,
 * Capistrano
 * Docker
 
+## Support
+
+Karafka has a [Wiki pages](https://github.com/karafka/karafka/wiki) for almost everything and a pretty decent [FAQ](https://github.com/karafka/karafka/wiki/FAQ). It covers the whole installation, setup and deployment along with other useful details on how to run Karafka.
+
+If you have any questions about using Karafka, feel free to join our [Gitter](https://gitter.im/karafka/karafka) chat channel.
+
 ## Getting started
 
 If you want to get started with Kafka and Karafka as fast as possible, then the best idea is to just clone our example repository:
@@ -40,20 +55,6 @@ and follow the instructions from the [example app Wiki](https://github.com/karaf
 
 If you need more details and know how on how to start Karafka with a clean installation, read the [Getting started page](https://github.com/karafka/karafka/wiki/Getting-started) section of our Wiki.
 
-## Support
-
-Karafka has a [Wiki pages](https://github.com/karafka/karafka/wiki) for almost everything. It covers the whole installation, setup and deployment along with other useful details on how to run Karafka.
-
-If you have any questions about using Karafka, feel free to join our [Gitter](https://gitter.im/karafka/karafka) chat channel.
-
-Karafka dev team also provides commercial support in following matters:
-
-- Additional programming services for integrating existing Ruby apps with Kafka and Karafka
-- Expertise and guidance on using Karafka within new and existing projects
-- Trainings on how to design and develop systems based on Apache Kafka and Karafka framework
-
-If you are interested in our commercial services, please contact [Maciej Mensfeld (maciej@coditsu.io)](mailto:maciej@coditsu.io) directly.
-
 ## Notice
 
 Karafka framework and Karafka team are __not__ related to Kafka streaming service called CloudKarafka in any matter. We don't recommend nor discourage usage of their platform.
@@ -64,55 +65,25 @@ Karafka framework and Karafka team are __not__ related to Kafka streaming servic
 * [Karafka Travis CI](https://travis-ci.org/karafka/karafka)
 * [Karafka Coditsu](https://app.coditsu.io/karafka/repositories/karafka)
 
-## Note on Patches/Pull Requests
+## Note on contributions
 
-Fork the project.
-Make your feature addition or bug fix.
-Add tests for it. This is important so we don't break it in a future versions unintentionally.
-Commit, do not mess with Rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull). Send me a pull request. Bonus points for topic branches.
+First, thank you for considering contributing to Karafka! It's people like you that make the open source community such a great community!
 
-[![coditsu](https://coditsu.io/assets/quality_bar.svg)](https://app.coditsu.io/karafka/repositories/karafka)
+Each pull request must pass all the rspec specs and meet our quality requirements.
 
-Each pull request must pass our quality requirements. To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combinse multiple linters and code analyzers for both code and documentation.
+To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combines multiple linters and code analyzers for both code and documentation. Once you're done with your changes, submit a pull request.
 
-Unfortunately, it does not yet support independent forks, however you should be fine by looking at what we require.
+Coditsu will automatically check your work against our quality standards. You can find your commit check results on the [builds page](https://app.coditsu.io/karafka/commit_builds) of Karafka organization.
 
-Please run:
-
-```bash
-bundle exec rake
-```
-
-to check if everything is in order. After that you can submit a pull request.
+[![coditsu](https://coditsu.io/assets/quality_bar.svg)](https://app.coditsu.io/karafka/commit_builds)
 
 ## Contributors
 
-This project exists thanks to all the people who contribute. [[Contribute]](CONTRIBUTING.md).
+This project exists thanks to all the people who contribute.
 <a href="https://github.com/karafka/karafka/graphs/contributors"><img src="https://opencollective.com/karafka/contributors.svg?width=890" /></a>
 
-## Backers
-
-Thank you to all our backers! 🙏 [[Become a backer](https://opencollective.com/karafka#backer)]
-
-<a href="https://opencollective.com/karafka#backers" target="_blank"><img src="https://opencollective.com/karafka/backers.svg?width=890"></a>
-
-
 ## Sponsors
 
-We are looking for sustainable sponsorship. If your company is relying on Karafka framework or simply want to see Karafka evolve faster to meet your requirements, please consider backing the project. [[Become a sponsor](https://opencollective.com/karafka#sponsor)]
-
-Please contact [Maciej Mensfeld (maciej@coditsu.io)](mailto:maciej@coditsu.io) directly for more details.
-
-
-<a href="https://opencollective.com/karafka/sponsor/0/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/0/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/1/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/1/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/2/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/2/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/3/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/3/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/4/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/4/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/5/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/5/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/6/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/6/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/7/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/7/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/8/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/8/avatar.svg"></a>
-<a href="https://opencollective.com/karafka/sponsor/9/website" target="_blank"><img src="https://opencollective.com/karafka/sponsor/9/avatar.svg"></a>
-
+We are looking for sustainable sponsorship. If your company is relying on Karafka framework or simply want to see Karafka evolve faster to meet your requirements, please consider backing the project.
 
+Please contact [Maciej Mensfeld](mailto:maciej@coditsu.io) directly for more details.