| Great question! We wrote about this in our blog post: https://www.featureform.com/post/feature-stores-explained-th... Feast is a literal feature store. it exclusively stores features, it does not manage the transformations used to compute them. The pros and cons of Feast are more obvious when examining the process to change a feature. It happens in three steps: 1. Write and run your new data transformation in your existing transformation pipeline. Note that this happens outside of Feast. 2. A new feature table must be created in Feast, since the old one cannot be directly overwritten. Once the new feature is created the transformation pipeline should be re-run and write all the features to the new table. 3. All the models that use this new feature should be updated to point at the new feature. Feast also has other problems, for example, it can’t copy your features from the offline to the online store, you have to download the features and upload them to the online store yourself using their CLI tool. You also have to manage retries and failure yourself. Featureform treats the transformation lineage as part of the feature and orchestrates your infrastructure to create and change your features. |