About The Architecture

Glasswall's REST API enables real-time responses to analysis and file rebuild requests.

A single API request is issued to sanitize a file and to receive a file analysis report.

The Glasswall API runs on a Kubernetes cluster with a group of microservices.

How it works

1. A file is sent to the REST API
2. The file is stored on a persisted volume within the cluster
3. A message is sent to the engine service to process the file
4. The engine service receives the message to process a file
5. That file is read from the persisted volume and is then processed by the Glasswall engine
6. The clean file and analysis report are then stored in the persisted volume
7. A message is sent to the report aggregator so the engine report can be generated
8. A message is then sent back to the API from an engine service
9. The API receives the message from an engine and reads either the clean file, report or both from the persisted volume and generates the correct response to the client.
10. A message is then sent to the report aggregator from the API
11. The report aggregator receives this message and generates a report from the analysis file and the API
12. Reports are then uploaded to the configured storage
13. Finally the original file, clean file and analysis report are deleted from the persisted volume

Scaling

All services use Kubernetes Event Drive Auto-Scaling (KEDA) to ensure that the right number of services are available based on the number of requests and file processing time within the platform.