-
Notifications
You must be signed in to change notification settings - Fork 427
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
week 4: presentation proposal (#2482)
Co-authored-by: Florian Immig <[email protected]>
- Loading branch information
Showing
1 changed file
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Assignment Proposal | ||
|
||
|
||
## Title | ||
|
||
What is a Feature Store in ML? | ||
|
||
## Names and KTH ID | ||
|
||
- Prerna Gupta ([email protected]) | ||
- Florian Jerome Immig ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 4 | ||
|
||
## Category | ||
|
||
- Presentation | ||
|
||
## Description | ||
|
||
We want to do a presentation on the concept of the Feature Store. We will explain the significance of using a feature store when dealing with MLOps workflows and present its advantages. Specifically we will talk about how it enhances real-time (online) applications. In our presentation we use Feast as an example for an open-source feature store and provide according code-snippets. | ||
|
||
**Relevance** | ||
|
||
When not having a feature store, ML feature reusability is limited and ML engineers spent a significant amount of time on feature engineering. The concept of a feature store acts as a hub of callaboration and ensures consistency accross training and serving avoiding training-serving skew. Furthermore, features can be reused accross teams leading to additional time savings. Feature stores allow for a consistent and fast delivery of feature values in online, offline and training scenarios. |