Introduction of IceWarp Microservices

With the release of IceWarp EPOS, microservices are taking on an increasingly important role within the IceWarp product family. While customers don't need to understand the technical details of how microservices operate to run their IceWarp server, a brief overview is provided below for context, applicable to both on-premises and cloud environments.

DASHBOARD

It is a cloud service that allows you to access your notes and documents from any device.

1. The user’s browser requests the server to open Dashboard/Notes in the WebClient.
2. Dashboard/Notes Interface is uploaded from the Interface Microservices Cloud.
3. API Microservice Cloud requests data from the server and transforms it into a form readable for Dashboard.
4. As soon as the data received from the server is transformed, API Microservices sends it to the user’s browser.

Issues may arise in Step 3, specifically in the communication between the server and the Microservices API. If the API is unable to access the server due to network problems, the application icon may not be displayed.

Since data is stored on the server in a format that is not directly readable by the user interface (it must be retrieved via the Interface Microservices), it requires transformation by the API Microservices. Any changes made by users are first sent to the API Microservices, where they are converted into a suitable format for storage and then transmitted back to the server.

The Dashboard is a cloud-based microservice that does not store any user data on the on-premises server, except for background images.

WEBDOCUMENTS

This service enables you to create, store, and collect all your documents, spreadsheets, presentations, and other files in one place. You can pin any file to your Dashboard. The selected files, like text documents, presentations or spreadsheets, can also be edited directly in the web browser.

When a user edits a document, the file is securely transferred to the Microservices Cloud via an encrypted channel. There, it is unpacked and opened in the WebClient application, offering the full range of editing functionality. Once the changes are completed, the updated file is sent back to the server and stored.

1. The user's browser sends a request to open WebDocuments in the WebClient, which are stored on the IceWarp server (either on-premises or in the cloud). The server then delivers the documents directly to the user's browser.
2. If the user begins editing a document, the server forwards the request to the WebDocuments Interface Microservices Cloud and transmits the file for processing. In the Microservices Cloud, the document is unpacked and rendered in the user's browser with full editing functionality.
3. The server loads the WebClient interface and transforms the data to be displayed in the user's browser.
4. A firewall on the server side controls incoming traffic. In some cases, it may block the connection between the server and the Microservices Cloud. Communication between the server and Microservices occurs over HTTPS, so the relevant port must be open to allow incoming traffic.
5. Since the connection is initiated by the server rather than by the Microservices, it is generally more likely to succeed.

CONFERENCES

The Conferences are WebRTC-powered, allowing you to arrange voice and video calls directly from the IceWarp chat window, enabling non-text-based communications with individuals or groups.

1. The browser sends a request to open Conferences in the WebClient, which is hosted on the IceWarp server—either on-premises or in the cloud.
2. The server interacts with the Cloud Microservices as it would with a database, triggering the launch of an entirely new application in the user's browser. No data is processed within the Microservices Cloud—it simply facilitates the opening of the application.

Conferences are scheduled on the server, while all user interactions take place in the Microservices Cloud, which hosts only the user interface. All meeting-related data—such as schedules, contacts, and history—is stored on the server.

RECORDINGS

Recordings are a key feature of Conferences, enabling you to capture meetings for later playback—ideal for reviewing discussions or sharing with others.

This feature is optional, and all recordings are stored in the Cloud. You can easily download them at any time within the last 30 days via the WebClient interface.

CENTRAL API

Secures communication between the IceWarp cloud and the user.

Since the data is stored on the server in a format which is not readable by the user’s interface (downloaded from the Interface Microservices), it must be transformed by the API Microservices.

Any changes made by users are sent to the API Microservices, which transform them into a form suitable for storage and then return them to the server.