Skip to content

Releases: apache/rocketmq-client-go

rocketmq-client-go-2.0.0-alpha2

07 Aug 03:05
f38894a
Compare
Choose a tag to compare
Pre-release

The main goal of this release is to support some new features, e.g. send a message by async model and pull consumer. and besides this, the release also will bring some unit tests for functionality.

Many features have not an independent issue, you can find them in Roadmap issue: 2.0.0-alpha2 Roadmap

Feature

  • [PR-86] - Support Interceptor
  • [PR-96] - Support multiple NameServer
  • [PR-102] - Support QueueSelector
  • [PR-100] - Support SendAsync
  • [PR-106] - Support PullConsumer
  • [PR-113] - Support Statistics of client
  • [PR-115] - Support order message in PushConsumer
  • [PR-117] - Support ACL
  • [PR-119] - Support retry when consume failed in PushConsumer

Improvement

  • [ISSUE-93] - refactor API to make more usability.
  • [PR-107] - return an error in start() instead of fatal directly
  • [PR-109] - add unit test for producer
  • [PR-116] - add unit test for internal/route.go

Bug

  • [ISSUE-65] - Fixed the issue that Missing Tag and Properties in Message when use producer.
  • [PR-97] - Fixed the issue that The timeout of RPC doesn't work and The InvokeAsync doesn't work

rocketmq-client-go-2.0.0-alpha1

21 May 02:18
Compare
Choose a tag to compare
Pre-release

This release is the first go native client for Apache RocketMQ,
it support:

  • sending message in synchronous mode
  • sending message in oneway mode
  • consuming message using push model

rocketmq-client-go-1.2.0

09 Jan 11:31
Compare
Choose a tag to compare

This release is the first initial golang client of rocketmq. It is based on the kernel of the CPP client and uses cgo to encapsulate the API Implementation of C.
The current version provides the following functions:

  1. support reliable synchronous sending of messages;
  2. support reliable orderly sending of messages;
  3. support reliable push consuming model;
  4. support default cluster consuming;
  5. support delayed messages;
  6. support reliable pull consuming model;
  7. support custom message properties;
  8. support message compression.
  9. support oneway sending of messages;