Skip to content
Gilang Adrian

— Case study

On-Demand Reporting — From 12 Minutes to 2

Upgraded report processing to Java 21 virtual threads, reducing on-demand generation time by 83% and peak thread usage by 75%.

Role
Product Engineer — Reporting & Settlement Systems
Period
During Reporting role · Nov 2023 – Present
Stack
Java 21 · Spring Boot · Virtual Threads

Business need

Users requesting reports on demand had to wait around 12 minutes for generation. Improving that wait was a concrete product performance goal, alongside reducing the resource demands of report processing.

My contribution

I combined reporting product ownership with engineering execution to upgrade report processing to Java 21 virtual threads. My broader delivery responsibility included requirements, acceptance criteria, functional validation, and release coordination with engineering, QA, and business stakeholders.

Results

  • On-demand report generation time reduced from 12 to 2 minutes, an 83% reduction.
  • Peak thread usage reduced by 75%.

The generation-time result applies to on-demand reports. Scheduled delivery to 431+ merchants is a separate reporting capability and scale measure.

Further delivery planning

I planned and scoped a secure report-delivery API route with engineering alongside email and SFTP. The API work remains a planning and scoping contribution in this case study.