# Online store

Feast uses online stores to serve features at low latency. Feature values are loaded from data sources into the online store through *materialization*, which can be triggered through the `materialize` command.

The storage schema of features within the online store mirrors that of the original data source. One key difference is that for each [entity key](https://docs.feast.dev/v0.36-branch/getting-started/concepts/entity), only the latest feature values are stored. No historical values are stored.

Here is an example batch data source:

![](https://content.gitbook.com/content/hGjX1Vpr09suK4XWalfg/blobs/QEMW5zFH1UNY04xFCUNc/image%20\(6\).png)

Once the above data source is materialized into Feast (using `feast materialize`), the feature values will be stored as follows:

![](https://content.gitbook.com/content/hGjX1Vpr09suK4XWalfg/blobs/6L0tKZNO9TcEJ8nezd01/image%20\(5\).png)

Features can also be written directly to the online store via [push sources](https://docs.feast.dev/v0.36-branch/reference/data-sources/push) .