Context
In 2024 I built a payment live dashboard and a checkout live monitor for the ed-tech platform. They were for schools and the operations team who needed to see payments and checkout health as they happened. I was the full-stack implementer.
The problem
Schools and ops could not see payments and checkout health in real time. Problems showed up late, through support tickets rather than a screen.
What I did
The work cut across five repositories, April to June 2024.
In the analytics warehouse I wrote the StarRocks views that the dashboard reads.
In the Rails backend I added the purchase insight type and the queries behind it.
In the low-code admin framework I built the payment live dashboard and the checkout live monitor, and added a pricing-plan cell to the admin app.
I also made a related change in the learner app.
Key decision
I chose to build on the existing low-code admin framework and the analytics warehouse instead of a separate service. That kept the dashboards inside tools the team already ran.
The trade-off is that I was bound by the framework's widgets, but there was nothing new to host or secure.
Result
Both dashboards shipped, giving live payments and checkout health across the five repositories.
What I learned
I would again build the data view first and the screen second. Next I would count how often the dashboards are opened and which alerts lead to action.
Stack
- StarRocks
- Ruby on Rails
- GraphQL
- React
- SQL
