Download PDF
Cube Dev > Case Studies > Cuboh's Transformation: From Latency to Efficiency with Cube
Cube Dev Logo

Cuboh's Transformation: From Latency to Efficiency with Cube

Technology Category
  • Application Infrastructure & Middleware - Database Management & Storage
  • Infrastructure as a Service (IaaS) - Cloud Databases
Applicable Industries
  • Buildings
  • Construction & Infrastructure
Use Cases
  • Time Sensitive Networking
Services
  • System Integration
The Challenge

Cuboh, a restaurant-tech company, integrates delivery apps with point-of-sales systems and consolidates them into a single tablet. Despite processing over $1B in transactional volume, the company faced a significant challenge. They hadn't built their data structure to handle scale, leading to inefficiencies in querying their database for millions of rows. This resulted in latency in large customer reporting requests. The team sought to create an appropriate underlying dataset to streamline their ledger-based reporting. They initially opted for a Kafka-based streaming platform, but soon realized they needed a more robust solution to handle their large datasets. The ideal solution needed to be compatible with an underlying relational database, produce low latency requests, handle RESTful API requests, provide near-real-time reporting, be self-managed, and offer caching for date-based query structures.

About The Customer

Cuboh is a seed-stage restaurant-tech company based in British Columbia, Canada. The company offers a SaaS that integrates delivery apps with point-of-sales systems, consolidating them into a single tablet. This technology also provides centralized reporting and menu management. Cuboh serves traditional restaurants, ghost kitchens, and chains, saving them from the complexities of delivery processing. The platform has processed over $1B in transactional volume, equating to over 50 million orders. Despite being a relatively small company with 51-100 employees, Cuboh has a significant market fit and demand.

The Solution

Cuboh discovered Cube in early 2022 and recognized its potential to address their challenges. Cube's heavy caching capabilities for date-based query structures were particularly appealing. Two team members facilitated Cube’s implementation on top of Cuboh’s IT infrastructure as a microservice that runs on its own AWS EC2 instance, all within less than a year. Cube’s compatibility with relational databases, its instant RESTful API, and its advanced, two-level caching system met Cuboh’s technical requirements. This allowed them to provide efficient reporting to their customers while reducing costs. Cube’s pre-aggregation structure resulted in fewer query metrics directly hitting the database, reducing the time required to generate real-time and historical reports from tens of seconds to less than 2. The team also found that endpoint querying and structuring reports were much easier with Cube, eliminating the need for writing additional back-end code to support specific endpoints.

Operational Impact

  • The implementation of Cube has significantly improved Cuboh's operational efficiency. The latency issues that plagued the company's large customer reporting requests have been resolved, leading to faster and more efficient reporting. The compatibility of Cube with relational databases and its instant RESTful API has streamlined Cuboh's operations. The advanced, two-level caching system has also reduced the load on the database, further enhancing performance. Additionally, the ease of endpoint querying and structuring reports with Cube has simplified the process, eliminating the need for additional back-end code. This has not only improved operational efficiency but also reduced costs.

Quantitative Benefit

  • Reduced time to generate real-time and historical reports from tens of seconds to less than 2 seconds

  • Processed over $1B in transactional volume, equating to over 50 million orders

  • Saved 14 weeks of engineering time

Related Case Studies.

Case Study
IoT System for Tunnel Construction
The Zenitaka Corporation ('Zenitaka') has two major business areas: its architectural business focuses on structures such as government buildings, office buildings, and commercial facilities, while its civil engineering business is targeted at structures such as tunnels, bridges and dams. Within these areas, there presented two issues that have always persisted in regard to the construction of mountain tunnels. These issues are 'improving safety" and "reducing energy consumption". Mountain tunnels construction requires a massive amount of electricity. This is because there are many kinds of electrical equipment being used day and night, including construction machinery, construction lighting, and ventilating fan. Despite this, the amount of power consumption is generally not tightly managed. In many cases, the exact amount of power consumption is only ascertained when the bill from the power company becomes available. Sometimes, corporations install demand-monitoring equipment to help curb the maximum power demanded. However, even in these cases, the devices only allow the total volume of power consumption to be ascertained, or they may issue warnings to prevent the contracted volume of power from being exceeded. In order to tackle the issue of reducing power consumption, it was first necessary to obtain an accurate breakdown of how much power was being used in each particular area. In other words, we needed to be able to visualize the amount of power being consumed. Safety, was also not being managed very rigorously. Even now, tunnel construction sites often use a 'name label' system for managing entry into the work site. Specifically, red labels with white reverse sides that bear the workers' names on both sides are displayed at the tunnel work site entrance. The workers themselves then flip the name label to the appropriate side when entering or exiting from the work site to indicate whether or not they are working inside the tunnel at any given time. If a worker forgets to flip his or her name label when entering or exiting from the tunnel, management cannot be performed effectively. In order to tackle the challenges mentioned above, Zenitaka decided to build a system that could improve the safety of tunnel construction as well as reduce the amount of power consumed. In other words, this new system would facilitate a clear picture of which workers were working in each location at the mountain tunnel construction site, as well as which processes were being carried out at those respective locations at any given time. The system would maintain the safety of all workers while also carefully controlling the electrical equipment to reduce unnecessary power consumption. Having decided on the concept, our next concern was whether there existed any kind of robust hardware that would not break down at the construction work site, that could move freely in response to changes in the working environment, and that could accurately detect workers and vehicles using radio frequency identification (RFID). Given that this system would involve many components that were new to Zenitaka, we decided to enlist the cooperation of E.I.Sol Co., Ltd. ('E.I.Sol') as our joint development partner, as they had provided us with a highly practical proposal.
Learn more
© 2015-2024 IoT ONE Limited | Privacy Policy

Contact us

Let's talk!

* Required
* Required
* Required
* Invalid email address
By submitting this form, you agree that IoT ONE may contact you with insights and marketing messaging.
No thanks, I don't want to receive any marketing emails from IoT ONE.
Submit

Thank you for your message!
We will contact you soon.