Rethinking the Feature Store concept for MLOps
Today we talk about Feature Stores. The recent Databricks acquisition of Tecton raised an interesting question for us: can we make a feature store work with any infra just as easily as a dedicated system using IOblend? Let’s have a look.
How a Feature Store Works Today
Machine learning teams agree on one thing: features are the most important input to a model. They need to be fresh, consistent, based on quality data and governed — across both training and inference.
This is the problem “feature stores” were invented to solve. By standardising feature definitions, providing a registry, and separating offline training data from online serving, they’ve become a common pattern in ML infrastructure.
But there’s a catch. Most feature stores introduce a new layer of infrastructure:
- A dedicated online store (often Redis, Dynamo, Tecton or Cassandra).
- An API service for serving features in real-time.
- A registry and metadata service.
- Synchronisation pipelines to keep online and offline stores consistent.
This works — but it comes at a cost. Teams end up paying for additional cloud services (platform costs + compute), debugging consistency issues between “the store” and “the warehouse,” and managing ingest tools to bring data into the said platforms. In some cases, the effort to run the feature store rivals the effort to run the models themselves.
So the question is worth asking: do we really need a separate store?
Rethinking the Pattern
If we step back, the essentials of a feature store boil down to five capabilities:
- Definitions — how features are built.
- A registry — metadata, lineage, and versioning.
- Offline storage — historical features for training.
- Online access — low-latency serving for inference.
- Freshness and correctness — keeping features aligned across training and serving.
Nothing on that list says you must use a secondary storage system. What you really need is a way to:
- Continuously process raw data into features.
- Materialise those features into your existing lake or warehouse.
- Guarantee governance, lineage, and point-in-time correctness.
- Serve them with the right latency for your application.
That raises an interesting alternative: what if the warehouse itself could be the feature store?
Continuous Features Without Extra Infrastructure
This is where IOblend’s design comes in. Built as a streaming-first DataOps engine (rather than a batch system adapted for streaming), it already provides the primitives that feature stores aim to deliver — but without standing up a new stack.
- Sub-second freshness — pipelines run continuously, not in micro-batches.
- Network-bound P99 latency — feature updates propagate almost instantly.
- >1 million TPS sustained — proven in production deployments.
- Governance by default — lineage, CDC handling, schema evolution, SCD, and drift monitoring are built into every pipeline.
- Runs in your environment — on-prem, VPC, or edge. No SaaS dependencies in the inference path.
In this architecture, the warehouse becomes the store. IOblend continuously maintains features inside Delta, Iceberg, Hudi, Snowflake, BigQuery, and others — the systems you already run.
The ROI of “No Store”
By eliminating the need for a separate feature store tier, you reap see benefits across several dimensions:
- Infrastructure cost savings — no Redis/Dynamo clusters, no duplication of data between “online” and “offline” stores.
- Performance at scale — P99 inference latencies and million-TPS throughput without extra serving infrastructure.
- Operational simplicity — ingestion, transformation, governance, and materialisation all in one engine.
- Data security and compliance — features stay inside your environment; no regulated data leaves your boundary.
A Dataflow in Practice
- Ingest — CDC from operational databases and event streams (Kafka, Kinesis, IoT).
- Process — streaming pipelines apply joins, aggregations, deduplication, slowly changing dimensions, and CDC merges with exactly-once semantics.
- Materialise — features continuously upserted into warehouse/lake tables (Delta, Iceberg, Hudi, Snowflake, BigQuery, etc.).
- Consume — applications query those tables directly. For ultra-low latency (<5ms), a lightweight cache or gateway can be layered on top.
Something to Think About
The idea behind feature stores is sound: models need features that are fresh, correct, and consistent. But the conventional implementation — running a parallel online store — is not the only way to achieve this.
A streaming-first engine that maintains features directly in your warehouse can deliver the same guarantees — with fewer systems, lower costs, and proven production performance at scale.
That’s the approach we’ve taken with IOblend: a feature store without the store.
IOblend presents a ground-breaking approach to IoT and data integration, revolutionizing the way businesses handle their data. It’s an all-in-one data integration accelerator, boasting real-time, production-grade, managed Apache Spark™ data pipelines that can be set up in mere minutes. This facilitates a massive acceleration in data migration projects, whether from on-prem to cloud or between clouds, thanks to its low code/no code development and automated data management and governance.
IOblend also simplifies the integration of streaming and batch data through Kappa architecture, significantly boosting the efficiency of operational analytics and MLOps. Its system enables the robust and cost-effective delivery of both centralized and federated data architectures, with low latency and massively parallelized data processing, capable of handling over 10 million transactions per second. Additionally, IOblend integrates seamlessly with leading cloud services like Snowflake and Microsoft Azure, underscoring its versatility and broad applicability in various data environments.
At its core, IOblend is an end-to-end enterprise data integration solution built with DataOps capability. It stands out as a versatile ETL product for building and managing data estates with high-grade data flows. The platform powers operational analytics and AI initiatives, drastically reducing the costs and development efforts associated with data projects and data science ventures. It’s engineered to connect to any source, perform in-memory transformations of streaming and batch data, and direct the results to any destination with minimal effort.
IOblend’s use cases are diverse and impactful. It streams live data from factories to automated forecasting models and channels data from IoT sensors to real-time monitoring applications, enabling automated decision-making based on live inputs and historical statistics. Additionally, it handles the movement of production-grade streaming and batch data to and from cloud data warehouses and lakes, powers data exchanges, and feeds applications with data that adheres to complex business rules and governance policies.
The platform comprises two core components: the IOblend Designer and the IOblend Engine. The IOblend Designer is a desktop GUI used for designing, building, and testing data pipeline DAGs, producing metadata that describes the data pipelines. The IOblend Engine, the heart of the system, converts this metadata into Spark streaming jobs executed on any Spark cluster. Available in Developer and Enterprise suites, IOblend supports both local and remote engine operations, catering to a wide range of development and operational needs. It also facilitates collaborative development and pipeline versioning, making it a robust tool for modern data management and analytics
Break Down the Data Walls with IOblend
Break Down the Data Walls with IOblend 📑 Did you know? It’s estimated that a whopping 80% of business data is just floating about, unstructured and stuck in siloed systems. Siloed data only brings value (if at all!) to the domain it belongs to. But the true value lies in the insights in brings to
Put a Stop to Data Chaos with IOblend Governed Integration
Put a Stop to Data Chaos with IOblend Governed Integration 🤯💥Did you know? By 2025, the global datasphere is projected to grow to 175 zettabytes? This staggering figure underscores the sheer scale of data businesses must manage, making simplification not just a luxury, but a necessity. Today, businesses don’t have a shortage of data. What
Optimising Customer Experience Through Real Time Data Sync
Optimising Customer Experiences Through Real Time Data Sync 🧠 Fun Fact: Did you know that 90% of the world’s data has been created in just the past two years? That’s a lot of information to manage – and a massive opportunity for businesses that know how to use it wisely. Understanding your customers is the
How Poor Data Integration Drains Productivity & Profits
How Poor Data Integration Drains Productivity & Profits Data is one of the most valuable assets a company can possess. We all know that (and if you still do not, god help you). Businesses rely on data to make informed decisions, optimise operations, drive customer engagement, etc. Data is everywhere and it’s waiting for us
How To Unlock Better Data Analytics with AI Agents
How To Unlock Better Data Analytics with AI Agents The new year brings with it new use cases. The speed with which the data industry evolves is incredible. It seems that the LLMs only appeared on the wider scene just a year ago. But we already have a plethora of exciting applications for it across
Why IOblend is Your Fast-Track to the Cloud
From Grounded to Clouded: Why IOblend is Your Fast-Track to the Cloud Today, we talk about data migration. Data migration these days mainly means moving to the cloud. Basically, if a business wants to drastically improve their data capabilities, they have to be on the cloud. Data migration is the mechanism that gets you there.
