Sanjay Bhansali

Sanjay Bhansali

Authored Publications
Sort By
  • Title
  • Title, descending
  • Year
  • Year, descending
    Mesa: Geo-Replicated, Near Real-Time, Scalable Data Warehousing
    Fan Yang
    Jason Govig
    Adam Kirsch
    Kelvin Chan
    Kevin Lai
    Shuo Wu
    Sandeep Dhoot
    Abhilash Kumar
    Mingsheng Hong
    Jamie Cameron
    Masood Siddiqi
    David Jones
    Andrey Gubarev
    Shivakumar Venkataraman
    Divyakant Agrawal
    VLDB(2014)
    Preview abstract Mesa is a highly scalable analytic data warehousing system that stores critical measurement data related to Google's Internet advertising business. Mesa is designed to satisfy a complex and challenging set of user and systems requirements, including near real-time data ingestion and queryability, as well as high availability, reliability, fault tolerance, and scalability for large data and query volumes. Specifically, Mesa handles petabytes of data, processes millions of row updates per second, and serves billions of queries that fetch trillions of rows per day. Mesa is geo-replicated across multiple datacenters and provides consistent and repeatable query answers at low latency, even when an entire datacenter fails. This paper presents the Mesa system and reports the performance and scale that it achieves. View details
    Searching for Build Debt: Experiences Managing Technical Debt at Google
    J. David Morgenthaler
    Misha Gridnev
    Proceedings of the Third International Workshop on Managing Technical Debt, IEEE(2012), pp. 1-6
    Preview abstract With a large and rapidly changing codebase, Google software engineers are constantly paying interest on various forms of technical debt. Google engineers also make efforts to pay down that debt, whether through special Fixit days, or via dedicated teams, variously known as janitors, cultivators, or demolition experts. We describe several related efforts to measure and pay down technical debt found in Google's BUILD files and associated dead code. We address debt found in dependency specifications, unbuildable targets, and unnecessary command line flags. These efforts often expose other forms of technical debt that must first be managed. View details