====== Jordan Stein ======
**Jordan Stein** is the Director of Product at nOps, a cloud optimization platform company. Stein is recognized for leading significant architectural decisions that modernized nOps's data infrastructure and engineering practices.

===== Role and Responsibilities =====
As Director of Product at [[nops|nOps]], Stein oversees product strategy and technical direction. In this capacity, Stein has been instrumental in evaluating and implementing data platform technologies that enhance the company's core offerings. The role involves making critical architectural decisions that affect how nOps processes, manages, and serves data to its customers in the cloud optimization space.

===== Databricks Lakebase Migration Leadership =====
Stein led the architectural decision to migrate nOps's data infrastructure to **Databricks Lakebase**, a lakehouse platform combining data warehouse and data lake capabilities. This migration represented a significant modernization initiative for the company's data engineering workflows (([[https://www.databricks.com/blog/how-nops-rebuilt-their-cloud-optimization-platform-databricks-lakebase-and-why-other-isvs|Databricks - How nOps Rebuilt Their Cloud Optimization Platform with Databricks Lakebase and Why Other ISVs Should Care (2026]])).

The migration addressed several technical limitations in nOps's previous architecture. A key benefit of the Lakebase platform was the elimination of scheduled jobs and cron-based batch processing, which had characterized traditional data pipeline approaches. By transitioning to Lakebase's **tight Lakehouse integration**, nOps achieved real-time data consumption capabilities, replacing time-delayed batch processes with continuous, event-driven data availability (([[https://www.databricks.com/blog/how-nops-rebuilt-their-cloud-optimization-platform-databricks-lakebase-and-why-other-isvs|Databricks - How nOps Rebuilt Their Cloud Optimization Platform with Databricks Lakebase and Why Other ISVs Should Care (2026]])).

===== Impact on Data Engineering Workflows =====
Stein's leadership on this architectural transition resulted in substantial improvements to nOps's data engineering operations. The elimination of scheduled batch jobs and dependency on cron-based scheduling represented a fundamental shift from periodic data updates to continuous data availability. This change enabled nOps to consume and process data in real-time, supporting faster analytics and reducing latency in cloud optimization insights delivered to customers (([[https://www.databricks.com/blog/how-nops-rebuilt-their-cloud-optimization-platform-databricks-lakebase-and-why-other-isvs|Databricks - How nOps Rebuilt Their Cloud Optimization Platform with Databricks Lakebase and Why Other ISVs Should Care (2026]])).

The modernization initiative exemplified broader industry trends toward [[lakehouse|lakehouse]] architectures, which unify the benefits of data lakes and data warehouses while reducing operational complexity. For nOps as an independent software vendor (ISV), this architectural evolution improved the company's ability to serve customers with more timely and responsive cloud cost optimization solutions.


===== See Also =====
  * [[nops|nOps]]
  * [[nous_research|Nous Research]]
  * [[cloud_cost_optimization|Cloud Cost Optimization]]

===== References =====