The following pages and posts are tagged with

TitleTypeExcerpt
Architecture overview Page The architecture chapter describes the overall architecture of Eclipse Ditto and in detail which sub-components fulfill which responsibilities. Top level component view This overview shows the Ditto services (components), the externally provided and consumed API endpoints, the external dependencies (MongoDB and nginx) and the relations of the services to...
Concierge service Page The “concierge” service is responsible for orchestrating the backing persistence services and for performing authorization of commands and command responses. It acts as a gatekeeper and entry point for other services providing APIs: gateway connectivity Those services do not need to be aware of...
Connectivity service Page Note: In Ditto 0.1.0-M2 the AMQP-Bridge service was added with the goal to be able to establish connections to Eclipse Hono as well as other AMQP 1.0 endpoints. With Ditto 0.3.0-M1 the AMQP-Bridge architecture became more modular and extensible to support additional...
Gateway service Page The “gateway” service is responsible for providing Ditto’s HTTP + WebSocket API. Model The gateway service has no model by its own, but uses the model of all the services it provides the HTTP + WebSocket API for. Signals The gateway service has no signals by...
Policies service Page The “policies” service takes care of persisting Policies. Model The model of the policies service is defined around the entity Policy: model Signals Other services can communicate with the policies service via: commands: containing commands and command responses which are processed...
Things-Search service Page The “things-search” service takes care of: updating an optimized search index of Things based on the events emitted by the things and policies services when entites are changed there executing search queries against the search index in order to find out which Things match...
Things service Page The “things” service takes care of persisting Things and Features. Model The model of the things service is defined around the entities Thing and Feature: model Signals Other services can communicate with the things service via: commands: containing commands...