Skip to content

Commit

Permalink
Added links to the two node types in the intro
Browse files Browse the repository at this point in the history
  • Loading branch information
tlberglund committed Nov 8, 2023
1 parent 411f0e5 commit c1929d7
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion basics/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,9 @@ Apache Pinot™ is a distributed OLAP database designed to serve real-time, user
## Distributed design principles

To accommodate large data volumes with stringent latency and concurrency requirements, Pinot is designed as a distributed database. As a distributed system, it has these goals:

* **Highly available**: Pinot has no single point of failure. When operators choose data replication, the cluster can continue to serve queries when a node goes down.
* **Horizontally scalable**: Operators can scale a Pinot cluster by adding new nodes when the workload increases. There are even two node types to scale query volume, query complexity, and data size independently.
* **Horizontally scalable**: Operators can scale a Pinot cluster by adding new nodes when the workload increases. There are even two node types ([servers](components/cluster/server.md) and [brokers](components/cluster/broker.md)) to scale query volume, query complexity, and data size independently.
* **Immutable data**: Pinot treats all stored data as if it is immutable, which gives designers the ability to make simplifying assumptions elsewhere in the system. However, Pinot still supports upserts on streaming entity data and background purges of data to comply with data privacy regulations.
* **Dynamic configuration changes**: Operations like adding new tables, expanding a cluster, ingesting data, modifying an existing table, and adding indexes do not impact query availability or performance.

Expand Down

0 comments on commit c1929d7

Please sign in to comment.