After many years, zkBox will be discontinued on June 1st, 2024.
Please make sure to retrieve your data as soon as possible.
Thank you for being part of this journey.

zkBox server internal structure

In this section you can find a brief presentation of the internal components of the zkBox server. The zkBox server consists of several modules; the most important are:
  • the web API component - responsible for receiving the requests and forward them to the core API module
  • the core API module - responsible for the entire business logic of the zkBox server; it's getting commands from the web and it's communicating with the data model layer
  • the data model layer - it's supporting the core API module by providing persistence capabilities; it's using the following main modules:
    • the caching component - a distributed cache across the nodes of the system to provide caching capabilities; it's used to reduce the trips to the storage layer
    • the data access layer - the persistence layer where the data is pushed to be actually stored; this layer can be either an AWS connector (to store the data into the Amazon cloud by using Amazon SimpleDB and Amazon S3) or an SQL connector (to store the data into a Microsoft SQL Server database)
The system is also using several 3rd party components to interact with the outside world.
Below you can see an image presenting the internal components of the zkBox server and their relations:
click to zoom
Please visit the downloads section for zkBox downloads.
If you would like to contribute (e.g. adding a new API client for another programming language, adding a new backend storage) feel free to contact us.