# 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 (either with specific timestamps or using `--disable-event-timestamp` to materialize all data with current timestamps).

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/master/getting-started/concepts/entity), only the latest feature values are stored. No historical values are stored.

Here is an example batch data source:

![](https://3095182975-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LqPPgcuCulk4PnaI4Ob-887967055%2Fuploads%2Fgit-blob-ac0d2d4c2f0034a273fae1fe979abbb4d4f5a1f7%2Fimage%20\(6\).png?alt=media\&token=b1844652-2d2d-45ce-b519-a53f3184635d)

Once the above data source is materialized into Feast (using `feast materialize` with timestamps or `feast materialize --disable-event-timestamp`), the feature values will be stored as follows:

![](https://3095182975-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LqPPgcuCulk4PnaI4Ob-887967055%2Fuploads%2Fgit-blob-700231a14936785ceda411190e509aa3c710d015%2Fimage%20\(5\).png?alt=media\&token=b23e6f0b-538a-4950-bf12-80d08f2e6cf6)

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