Architecture

The architecture of Cyclos 4 is based on three tiers, the user client , the Cyclos server and the database server.

User client

The first versions of Cyclos only had the web-RPC. It is used for the classic interface and it communicates directly with the service facade.After that, we developed the REST-interface. This is based on the Open-API standards and is much more consistent between versions. So, the web-RPC changes with each version of Cyclos, while we keep the REST-interface as stable as possible. With each new version of Cyclos, we will supply a list of changes. This way you can verify, whether the API interface will still be working.The REST-interface is used for the mobile app, the new user-interface and third-party software. In the near future, the REST-interface will become the default front-end. The classic interface will only be used for administrators.When you want Cyclos to do something which is not supported in the REST-interface, it is also possible to build a custom interface. But, in general, we recommend using the REST-interface.

Cyclos server

So, all calls are directed to the web-interface or the REST-interface, and are sent to the Service-Facade.

But before they can go anywhere else, they are directed to the Service-Security.The Service-Security performs a number of checks. For example, does the user have authorization to perform the operation? And is this the right user?Service-Security prevents users performing operations that are illegal.

Then, the request is transferred to the Service-Implementation. Here is where the real work is done, resulting in a request to the database.

We use the Java Persistence API for interfacing with the database. The Cyclos system runs entirely in a Tomcat web-container.

Database server

The Postgress database can be implemented on a separate server, thus allowing it to be scaled.

Architecture overview

You must be logged in to access this course