Since the last milestone of Eclipse Ditto 0.2.0-M1, the following changes, new features and bugfixes were added.
Changes
OpenJ9 based Docker images
The official Eclipse Ditto Docker images are now based on the Eclipse OpenJ9 JVM. With this JVM (cheers to the OpenJ9 developers for this awesome JVM) Ditto’s containers need a lot less memory having similar if not better throughput.
This especially comes in handy for the Ditto sandbox which only has 4GB RAM and 1 CPU core ;-)
AMQP bridge renaming
Ditto’s former AMQP bridge service was renamed to connectivity as it no longer only manages AMQP 1.0 connections, see
the new features.
New features
AMQP 0.9.1 connectivity
The new connectivity service can now, additionally to AMQP 1.0, manage and open connections to AMQP 0.9.1 endpoints
(e.g. provided by a RabbitMQ broker).
Payload mapping to/from Ditto Protocol
The new connectivity service can now also map message arbitrary text or byte payload from incoming AMQP 1.0 / 0.9.1
connections which are not yet in Ditto Protocol messages in such and can also map outgoing
Ditto Protocol messages (e.g. responses or events) back to some arbitrary text or byte payload.
Bugfixes
Failover and stability fixes in connectivity service
The former AMQP bridge did loose the connection to AMQP 1.0 endpoints. This is now much more stable from which also the new AMQP 0.9.1 connections benefit.
Docker compose config was wrong
The entrypoint/command was pointing to a wrong starter.jar.
Various smaller bugfixes
This is a complete list of the merged pull requests.
Documentation
The documentation for the new/renamed connectivity service now has its own new section:
Connectivity API.