The following pages in this section cover Data model, Ingestion pipeline, ClickHouse and Querying data. This document gives an overview of the general architecture. How our cloud or a deployed PostHog Helm chart works on Kubernetes.
Zooming right out
There are only a few systems to consider. A Website and API is presented for users. An API for Client Apps. A plugin service for processing events on ingestion. And a worker service for processing events in response to triggers (e.g. timers)
Starts to reveal the flow between parts of the system
Zoomed right in
No communication is needed into or out of this namespace other than the ingress controller for app and collecting data.
Note that the specifics of this may vary:
- ClickHouse, Kafka, PostgreSQL and Redis services may be hosted outside of the namespace or configured differently.
- The ClickHouse cluster is managed by clickhouse-operator and the exact number of pods vary according to sharding settings.