Author: AdheipSingh Sadhrao

For a couple of years, my journey has revolved around constructing control planes for data infrastructure startups. As an engineer, I have been fortunate to gain invaluable insights into the challenges and intricacies of developing successful SAAS products. Drawing from my firsthand experiences, this series of blog posts delve into the lessons learned and shares my goals at DataInfra, where I am building a centralized control plane for SAAS infrastructure. Join me as we explore the critical aspects and key considerations of constructing effective control planes in the dynamic and competitive SAAS industry.

Introduction

Before we delve into the content, let's address the ambiguity surrounding the term "Control Plane for SAAS Infrastructure." In the context of SAAS infrastructure, the control plane refers to the centralized system that governs and orchestrates the deployment, configuration, and operation of applications and services on data planes. Data Planes can exist within the SAAS provider's network or at the customer premise. By SAAS Infra, I specifically mean the service provisioning layer in a SAAS product.

As a seasoned professional, I have gained extensive experience as a maintainer of Apache Druid k8s operator and have co-authored and committed to various k8s operators/libraries. Through my experience, I have recognized the need to establish application-specific control planes to facilitate the smooth running of big data on Kubernetes.

In my past roles, I have built Kubernetes control planes for Druid at RillData, Pinot at Startree, and Clickhouse at Chistadata. Having worked on all three OLAP stores, I am now fully dedicated to my latest venture, DataInfra, a company focused on building highly efficient control planes that enable the seamless running of data on Kubernetes.