# Batch Materialization Engine

Note: The materialization engine is not constructed via unified compute engine interface.

A batch materialization engine is a component of Feast that's responsible for moving data from the offline store into the online store.

A materialization engine abstracts over specific technologies or frameworks that are used to materialize data. It allows users to use a pure local serialized approach (which is the default LocalComputeEngine), or delegates the materialization to seperate components (e.g. AWS Lambda, as implemented by the the LambdaComputeEngine).

If the built-in engines are not sufficient, you can create your own custom materialization engine. Please see [this guide](https://github.com/feast-dev/feast/blob/v0.50-branch/docs/how-to-guides/customizing-feast/creating-a-custom-compute-engine.md) for more details.

Please see [feature\_store.yaml](https://docs.feast.dev/v0.50-branch/reference/feature-repository/feature-store-yaml#overview) for configuring engines.