Restructurization of Ditto's maven modules in order to simplify/ease further development
It includes the following topics/enhancements:
Merge/PATCH updates of digital twins
Configurable OpenID Connect / OAuth2.0 claim extraction to be used for authorization
Establishing connections to endpoints (via AMQP, MQTT, HTTP) utilizing a Ditto managed SSH tunnel
Addition of a DevOps API in order to retrieve all known connections
Expiring policy subjects + publishing of notification message prior to expiry
Built-in acknowledgement for search updates to have the option of twin updates with strong consistency of the search index
Addition of policy actions in order to inject a policy subject based on a provided JWT
Restoring active connection faster after a hard restart of the Ditto cluster via automatic prioritization of connections
Support for LastWill/Testament + retain flag for MQTT connections
Provide JWT tokens to Websocket endpoint with browser APIs
The following notable fixes are included:
Fixing that "content-type" of a Ditto Protocol JSON message describes the content of the "value" of the message
Fixing password encoding/decoding for AMQP 1.0 connections when special characters like "+" were used
Fix merging "extraFields" into thing payload when using "normalization" mapper in connections
The following non-functional work is also included:
Improvement of stability during rolling updates
Addition of sharding concept for Ditto internal pub/sub enabling connection of e.g. tens of thousands websocket sessions
Background cleanup improvements in order to have less impact on DB rountrip times
Update of third party libraries (e.g. Akka)
Documentation of deployment via K3S
The project leadership certifies that the APIs in this release are "Eclipse Quality".
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.
There are no security issues known at the time of this writing.
A sandbox installation where Ditto can be tried out without setting it up locally
Conforms To UI/UX Guidelines:
Not applicable (project doesn't provide UI)
Ditto does not provide a UI yet.
End of Life:
Removal of API version 1
API version 1 and ACLs are removed in Ditto 2.0.
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.
Users of Ditto ask their questions via these channels: