Cinnamon architecture

Diagram

The following diagram shows the architecture of a Cinnamon system with its peripherals.

Components

Cinnamon Server

The server is the core Cinnamon component. Accessing all backend data and secondary services is exclusively done through the API. Thus, clients don't have and don't need access to the database, the content or the index directly, don't store backend credentials and can't bypass server functionality like permission checking. The API is complete in the sense that all client components like CDCplus, CAE or Change Trigger are implemented using API methods and nothing else.

The Cinnamon Server API is based on http(s)/XML. Find the documentation here: ​https://github.com/dewarim/cinnamon4/blob/master/docs/api.md

The API can be exposed through http or https. In the most simple case, the server listens on http, thus, client processes running on the same machine can access the server without encryption (avoiding issuing certificates for local traffix, which is convenient for test and development setups). By firewall settings, this can be restricted to local access and access from a web proxy and / or a VPN, where encryption is added. Alternatively, the server can be configured to listen only on https by itself. The API client supports both, including handling of self-signed certificates for internal traffic.

Database

Content

Index

tika

CAE

Change Trigger

CDCplus

Web Client

Other Clients

Other Servers