See the changelogs for MigratoryData server 6.x below. For API changelogs, refer to each API individually.

  • v6.0.21

  • This release addresses a bug in the Kafka Edition where, after a pause/resume, a client reconnects twice to the cluster before establishing a stable connection.

  • Includes additional minor enhancements.

  • v6.0.18

  • This release includes performance enhancements, mainly for interactive publishing extension.

  • v6.0.17

  • This release includes performance enhancements, mainly for Kafka extension (including updating the Kafka client library).

  • v6.0.16

  • This release exposes an improved Presence API for simpler use.

  • v6.0.15

    • This release includes essential maintenance fixes and introduces a new integration with Amazon Managed Streaming for Apache Kafka (MSK).
    • Enhanced documentation to support deployment automation using Docker, Kubernetes, or Terraform.

  • v6.0.14

    • Bug fixes and improvements for Kafka extension.

  • v6.0.13

    • Addressed an issue with the Interactive Publishing extension where a StringIndexOutOfBoundsException was thrown when handling subjects with only one segment. According to the documentation, subjects with one segment are valid, but the extension typically deals with subjects with two or more segments. This led to an exception being thrown when a subject with only one segment was used. More details can be found in the Interactive Publishing documentation.

  • v6.0.12

    • Minor fixes for Kafka extension.

  • v6.0.11

    • Introduced a new memory optimization feature, particularly useful for scenarios where new subjects are frequently added to your system but eventually become idle. This feature utilises a new parameter called SnapshotExpireTime and a new monitoring indicator called NumberOfSubjects.
    • The SnapshotExpireTime parameter allows you to define the number of seconds a snapshot message should be persisted in memory, helping to optimize memory usage. By default, snapshot messages are preserved indefinitely, but this parameter can be used to avoid memory waste for continuously introduced subjects that are not updated after a certain period. More details can be found in the History section.
    • The NumberOfSubjects indicator counts the number of active subjects, i.e., subjects with unexpired history. This is particularly beneficial if you have a large number of new subjects that become idle after a while, and if your MigratoryData server is configured to run without periodic restarts.

  • v6.0.10

    • Enhancements to the JWT Authorization Add-on with wildcard subjects.
    • Introduction of a new Interactive Publishing Add-on.

  • v6.0.9

    • Official support for the JSON Web Tokens (JWT) standard through a new off-the-shelf JWT Authorization add-on.

  • v6.0.8

    • Fixes and enhancements in the MigratoryData server.
    • Integration with the BoringSSL library.

  • v6.0.7

    • Minor fixes and improvements.

  • v6.0.6

    • Release of MigratoryData 6.0.6, which includes a new Kafka native add-on. This add-on allows for new use cases, leverages the Kafka ecosystem, and supports fully managed Kafka service providers. More details can be found in this blog post.

  • v6.0.5

    • Minor fixes and improvements.

  • v6.0.4


  • v6.0.3

    • This release includes bug fixes, enhancements. The most important enhancements are:
      • Add message compression for all MigratoryData client libraries
      • Add a new bidirectional publish/subscribe client library for PHP: MigratoryData Client for ReactPHP.

  • v6.0.2

    • This is mostly a bug-fix release but also completes the migration of all client libraries from MigratoryData 5.x to MigratoryData 6.x.

  • v6.0.1


  • v6.0.0

    • First release of MigratoryData Server version 6.