Architecture
An overview of the architecture for the DBNL platform
The DBNL platform architecture consists of a set of Services packaged as Docker images and a set of standard Infrastructure components that are deployed into your infrastructure (e.g. a VPC in AWS or GCP, or on-premise). The platform is scalable, modular, and self contained. It does not require an external connection to hosted Distributional services to operate.
Infrastructure
The DBNL platform requires the following infrastructure:
A Kubernetes cluster to host the DBNL platform services.
A PostgreSQL database to store metadata.
An object store bucket to store raw data (e.g. S3 or GCS).
A Redis database to serve as a messaging queue.
A load balancer to route traffic to the API or UI service.
(Optional) A Clickhouse database to store trace data.
Services
The DBNL platform consists of three core services that run within the Kubernetes cluster:
The API service (api-srv) serves the DBNL API and orchestrates work across the dbnl platform.
The worker service (worker-srv) processes async jobs scheduled by the API service.
The UI service (ui-srv) serves the DBNL UI assets.
Was this helpful?