Jobber's High-Performance Embedded Dashboards with Cube

Jobber is a leading provider of business management software, helping small home service businesses stay organized, connect with customers, grow revenue, and better compete against large corporations. The company's technology supports more than 50 industries, including HVAC, plumbing, lawn care, cleaning, and more. Since launching in 2011, businesses using Jobber have serviced over 15 million households in more than 47 countries. Today, more than 100,000 service professionals use Jobber's platform and rely on it to stay on top of—and grow—their businesses.

Jobber, a leading provider of business management software, supports over 50 industries and has serviced over 15 million households in more than 47 countries. A crucial tool for Jobber's customers is dashboards that provide a snapshot of their businesses, helping them schedule their day, optimize routing, keep track of invoices, accept payments, and more. However, as Jobber's business scaled and accumulated close to a decade of data, the dashboard performance began to slow down. The team tried to address these performance issues through caching, query optimization, and database tuning, but they realized that more needed to be done. The challenge was to find a solution that could handle the large amount of data and still deliver high-performance dashboards.

Jobber found a solution in Cube, a platform that offers flexibility and a two-level caching system. The Jobber team started using Cube almost as a black box, communicating with it and removing the optimization code they had to maintain in the past. Jobber's first use case with Cube involved using daily rollup pre-aggregations with the two-level caching. They also leveraged the external pre-aggregations capability of Cube, as their source database was a read-only database replica. Jobber's architecture involved a single PostgreSQL database backend, a read-only replica of the database to populate the rollup pre-aggregations database, and wrapping the Cube REST API with their own API for handling things like authentication. They also used multitenancy with a query transformer to enforce at runtime that all data queries filter to the authenticated tenant.

• The implementation of Cube in Jobber's system has significantly improved the performance of their dashboards. The two-level caching system of Cube has eliminated the need for Jobber to maintain their own optimization code, simplifying their operations. The external pre-aggregations capability of Cube has also been beneficial, as it allows Jobber to build pre-aggregations inline within their read-only source database. Furthermore, Jobber's active engagement with Cube's open-source community has not only accelerated their own development but also provided valuable insights to the Cube Dev team on actual use cases in production environments. The successful deployment of Cube has led Jobber to explore other areas where Cube can reduce engineering costs while delivering great features for their customers.

• Jobber supports over 50 industries and has serviced over 15 million households in more than 47 countries.

• More than 100,000 service professionals use Jobber's platform.

• Jobber's architecture involves a single PostgreSQL database backend, a read-only replica of the database to populate the rollup pre-aggregations database.