Eclipse Ditto™ 3.1.0

3.1.0

Description

Eclipse Ditto 3.1.0 focuses on the following areas:

  • Conditional message processing based on a specified condition targeting the twin state
  • Support for reading/writing AMQP 1.0 "Message annotations" in Ditto managed connections
  • Policy imports: Reference other policies from policies, enabling reuse of policy entries
  • Several Ditto explorer UI enhancements
  • Support for configuring an audience for Ditto managed HTTP connections performing OAuth2.0 based authentication

The following non-functional work is also included:

  • End-2-End graceful shutdown support, enabling a smoother restart of Ditto services with less user impact
  • Support for encryption/decryption of secrets (e.g. passwords) part of the Ditto managed connections before persisting to the database
  • IPv6 support for blocked subnet validation

The following notable fixes are included:

  • Fixing that known connections were not immediately started after connectivity service restart
Architectural Issues

Ditto's codebase is implemented in Java. By default Java objects are mutable which does not work well in highly scalable, message driven architectures, as possible side-effects during runtime may occur when concurrently modifying objects. Because of that the Ditto team decided to use immutable objects wherever and whenever possible. Immutablity of the objects is ensured in unit tests.

Ditto's model modules and also the Ditto Java client are OSGi bundles so that they may be used in OSGi environments without much effort. The model modules are configured to be checked by a "binary compatibility checker" in the Maven build so that APIs are not broken unintentionally.

On a level higher than the model, Ditto uses a microservice based architecture. As Ditto's microservices are interacting via an event driven approach, Ditto provides a very modular setup on the microservice level meaning that single services must be not started at all if their functionality is not needed. Another benefit from this architecture is that the services may be scaled horizontally if more resources are required.

Ditto utilizes the CQRS and EventSourcing pattern and mainly uses "inserts" (append only) into the database in favor to "updates" in order to get a better performance when doing database writes. The only exception is the "search" microservice which uses traditional CRUD in order to update its search index.

Security Issues

There are no security issues known at the time of this writing.

Non-Code Aspects

Ditto comes with:

Conforms To UI/UX Guidelines
Not verified
End of Life

None.

Standards

Ditto is able to process AMQP 1.0, AMQP 0.9.1, MQTT 3.1.1 and MQTT 5 messages which are all standardized (IoT) protocols.

Ditto can use JSON Web Tokens specified by RFC 7519 in order to extract "subjects" (e.g. a user-id) to use for the access control to twins.

Ditto's API documentation is defined using the OpenAPI specification 3.0.0 allowing both creation of an interactive HTML-based documentation and creation of skelettons for various programming languages based on that specification.

Ditto supports the W3C Web of Things (WoT) Thing Description 1.1 standard.

Communities

Users of Ditto ask their questions via these channels:

  • The Gitter chatroom of Ditto
  • Via GitHub discussions for questions and general discussions
  • A Stackoverflow tag "eclipse-ditto" on which community quersions are answered by our committers
  • The mailing-list (ditto-dev@eclipse.org) is not actively used and watched

Ditto seeks for a good integration with Eclipse Hono in order to being able to create digital twins for all devices connected via Hono. The Ditto team is also in regular discussion with the Hono team.

Some of the Ditto team are committers in the Eclipse IoT Packages project aiming to simplify deployment and integration between Eclipse Hono and Ditto and additionally to showcase the integration with other OSS IoT projects.

In order to adopt the W3C WoT (Web of Things) Thing Description standard, the Ditto team also collaborates with the W3C WoT Working Group, evolving the standard and providing feedback.