The APEER Architecture
The more our APEER image processing platform grows the greater the complexity becomes. In this section we want to share a big picture of the technical APEER architecture.


There are a lot of really good programming languages and libraries out there to perform image processing. Compared to other image processing software we do not want to force you to use a specific framework. We want to give you all the flexibility you need to concentrate on your image processing task. Therefore, we built the APEER platform on a strong base:
  • Scaleable cloud computation technology provided by Microsoft Azure
  • Customizable Docker containers to connect Modules to Workflows
  • Easy-to-use Arivis WebViewer to display even huge 3D images in realtime
  • Flexible Git version control system to upload your code and to enable collaboration

The Module Creation Process

The Path to your APEER Module
Upon that you are able build your APEER module using almost every programming language or library you want. We will provide you with a detailed recipe in the following sections, but first we need to learn about the ingredients of your new APEER module. Let's start with looking at the module creation process:
Let's assume that we want to make a new module on APEER. The base of our module is the code, which provides different functionalities and probably contains several components (e.g. external libraries, own written code or our APEER SDK). The code is wrapped by a Docker Specification file that creates a Docker container. This makes it easy to handle our module during runtime. Within APEER you have the possibility to use different in- and output parameters (files, images, numbers, texts etc.). In the current version of your module other users would not have any clue, how to use it in a workflow. Thus, specifying your in- and output parameters is crucial, which can be done in the Module Specification file. Now our module is almost ready to use. To finish your module and to let other APEER members understand you module it is important to add some documentation. For your APEER module this means to add some descriptions in the README file and to write a comprehensive summary of you module on APEER. Most of the users are more likely to make use of the module or extend it, when there is a good description of it.
Let's proceed with the next section to prepare your computer for the module creation.
Last modified 1yr ago