V1.4.0

HareMq 1.4.0 Release Notes

New features

• Stream queue support

  • Added stream-aware consumer/publisher mode.
  • stream: true consumption.
  • stream_offset support: "first", "last", "next" (default), integer, %DateTime{}.
  • Added stream integration tests.

• Retry/delay improvements

  • Added delay_cascade_in_ms config field:
    • List of per-retry delays, e.g. [1_000, 5_000, 30_000].
    • Allows granular retry delay schedules in addition to delay_in_ms.
  • Configuration normalized:
    • check_interval -> check_interval_ms
    • message_ttl -> message_ttl_ms

• AutoScaler / DynamicSupervisor improvements

  • Better dynamic scaling decisions.
  • Configurable worker call timeout.
  • Improved auto-scaler logging and error diagnostics.

• Consumer worker robustness

  • In-flight task tracking and drain handling.
  • Connection/channel monitor handling improved.

Stability improvements

• wait_for_messages default timeout changed from 5_000 to 10_000.
• wait_for_consumers default timeout changed from 5_000 to 10_000.
• Reduced slow/CI flakiness for RabbitMQ integration tests.

Bug fixes

• Fixed consumer_worker drain test variable warning.
• Fixed queue/exchange declaration behavior in consumers.
• Fixed JSON encoding errors in publisher payload handling.
• Fixed nil delay_in_ms / retry_limit handling in configuration.
• Fixed reconnect/consumer channel error logging and recovery paths.

Full Changelog: v1.3.0...v1.4.0

v1.3.0

Full Changelog: v1.2.0...v1.3.0

v1.2.0

What's Changed

• Dedup cache by @Dimakoua in #3
  This feature introduces a deduplication cache to prevent the publishing of duplicate messages. By implementing this cache, we can ensure that only unique messages are processed, improving efficiency and reducing potential errors caused by duplicate entries.

• Consumer scaling feature by @Dimakoua in #6
  This update adds the ability to scale consumers dynamically, allowing the system to handle varying workloads more efficiently. By scaling the number of consumers up or down based on demand, we can optimize resource usage and maintain performance under different loads.

Full Changelog: v1.1.0...v1.2.0

v1.1.0

What's Changed

• Dedup cache by @Dimakoua in #3

Full Changelog: v1.0.4...v1.1.0

v1.0.4

Full Changelog: v1.0.3...v1.0.4

v1.0.3

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Full Changelog: v1.0.1...v1.0.2

v1.0.1

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Full Changelog: v0.1.2...v1.0.0