Building the Best Data Pipelines
For technology leaders, the key question is no longer whether pipelines can move data faster, but who should own the rules for what is moved, when, and at what cost. As pipelines become more distributed and AI-ready, the management challenge shifts toward clearer decision rights across data, platform, security and business teams. Without that clarity, faster plumbing can simply accelerate inconsistent definitions, duplicated controls and avoidable rework.
This makes operating model design a priority, not a side issue. If data producers can tag, data engineers can transform, and business teams can consume the same asset, then the organisation needs explicit standards for lineage, quality thresholds, retention, and exception handling. The practical test is whether teams can resolve data disputes quickly, or whether every issue escalates into ad hoc negotiation. A shared glossary and semantic layer help, but only if someone is accountable for enforcing them.
There is also a portfolio trade-off that CIOs and transformation leaders need to surface early. Not every data flow warrants real-time treatment. Prioritising low-latency pipelines for high-value use cases while keeping other flows batch-oriented is a funding and architecture decision, not just a technical one. The useful next questions are: which business outcomes justify the extra cost of real-time processing, what metrics will prove value, and which pipelines can be deferred or simplified?
Finally, the shift toward automation and AI-assisted engineering changes the control environment. It can reduce bottlenecks, but it also raises the bar for testing, auditability and vendor oversight. Leaders should ask how changes will be reviewed, how pipeline errors will be detected in motion, and how ownership is divided when cloud services, streaming tools and data governance platforms come from different suppliers.
Non-Linear Data Pipelines
Krishna Subramanian, COO and co-founder of Komprise, explains via email that data today is being generated everywhere — edge, datacenter, and cloud. This means data processing should also be distributed, which means data pipelines must no longer require moving all the data to a central data lake first before processing. โThis requires new data pipeline techniques focused on unstructured data and AI,โ she says. This means the use of composable architectures, which allow modular and API-first data services, will enable companies to mix and match best-of-breed solutions for their data pipeline needs. Subramanian says the biggest evolution of data pipelines is the re-architecture to address unstructured data and AI. โWe will see a massive transformation in data indexing, data management, data pre-processing and data workflow technologies to address this massive emerging need,โ she says.Scaling Pipelines Across Multiple Sources
Rahul Rastogi, CIO at SingleStore, explains via email that scaling data pipelines can add extra layers of complexity when it comes to ensuring data accuracy, consistency, privacy, governance, and security across various sources — especially as more organizations become increasingly data hungry. He says when pipelines scale, it becomes more difficult to achieve low latency — a critical component to keep up with todayโs rapid pace — as it takes longer to process massive datasets.ย โThe underlying infrastructure such as the storage and compute must also scale effectively to meet the demands of increasing data pipelines,โ he says. Another consideration is meeting data privacy and governance standards, which can be difficult to keep up with as regulations continue to evolve. Rastogi says to overcome these obstacles, organizations must adopt scalable data platforms that are designed to handle large-scale data processing and use techniques like partitioning and sharding (which distributes data across multiple servers) to improve processing efficiency and scalability. โThey should also leverage cloud solutions that offer scalable infrastructure and storage, along with benefits like auto-scaling mechanisms to adjust resources based on workload demands,โ he adds.Real-Time Analytics, Improved Collaboration
Rastogi notes real-time analytics play a critical part in optimizing data pipelines. โDetection and actioning enable data issues to be addressed in real-time, allowing businesses to make actionable insights and adaptive strategies,โ he says. For organizations to experience these benefits, theyโll need to deploy a data platform that can process data in milliseconds instead of minutes, all the while detecting data quality, anomalies, and completeness issues while the data is in motion. He adds that data collaboration between various data teams is critical to ensure everyone involved is speaking the same language. Itโs important that data teams have a common understanding of data definitions for both measures and dimensions and a common platform for processing the data — for example building and extending pipelines. Rastogi explains while it is relatively easy to drive standardization of data processing technologies and data platforms, companies should consider data cataloging solutions and glossaries to drive consistency of data definitions. โAnother consideration is implementing enterprise semantic layers by subject areas, and investing in processes through data champions to ensure everyone is interpreting the data in the same way,โ he notes. Having all the data in one place also spurs collaboration and presents opportunities for data organizations to create common integrated data structures that can be used by data scientists to train models or by application developers to build intelligent applications. Subramanian points out data pipelines can create data workflows between data science teams, IT and business units. โImagine if users who generate data can tag the data which is then leveraged by data scientists for analytics while IT manages the data lifecycle,โ she says. โThis is a three-way collaboration on the same data facilitated by smart data workflows leveraging data pipelines.โData Pipelines of the Future
Rastogi says the data pipeline architecture of the future will feature a growing emphasis on stream processing and low-latency data platforms for real-time insights, enabled by tools like Kafka, Flink, and Kinesis. However, not all data needs to be processed in real-time — enterprises can adopt a hybrid approach to balance performance and cost. He predicts data operations (DataOps) and automation would gain traction as companies apply software engineering principles to data management — a principle that was not followed before.ย โEnterprises should also consider cloud-native architectures, utilizing serverless services and scalable cloud databases to handle large, bursty data volumes and scale,โ he says. He points to AI-powered data engineering, enabling data analysts to assemble and create data pipelines without the knowledge and expertise in writing code, as another exciting trend. โHowever, data quality and pipeline accuracy will be critical,โ Rastogi says. โStarting small, learning and scaling gradually is the best approach.โ Subramanian says she thinks the biggest evolution of data pipelines is the re-architecture to address unstructured data and AI. โWe will see a massive transformation in data indexing, data management, data pre-processing and data workflow technologies to address this massive emerging need,โ she says.Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.
