Data pipelinesCustomer support
TicketDesk-AI
A support desk on Databricks Lakebase, built like a trading terminal
180tests, run against a real Postgres database
See the code on GitHub (opens in a new tab)
Proof you can check:Code on GitHub
Data pipelines
Tickets and analytics on one platform
- Monitor flickers on the second display5m45s
- SSO login loop on the analytics dashboard22h54m
- VPN disconnects every few minutes2d18h
- Payroll export fails for contractors5d06h
Lubo Bali · lubobali.com
The problem
Support tickets need a database that never loses a message and never lets two people change one ticket at the same moment. Analytics tables can't promise that.
What I built
A ticket desk on Databricks Lakebase: live SLA clocks, priority signals and keyboard shortcuts. Every change also flows into Delta tables for analytics, with no extra connector.
Tech & why
Lakebase gives the app real rows, keys and rules; Change Data Feed gives analysts the full history next to it. One platform, both jobs.
- Databricks Lakebase
- PostgreSQL
- Flask
- Python
- Delta Lake
The result
A working desk running as a Databricks App, 180 tests on a real Postgres (no fake database), and an analytics history that fills itself.
See the real app
Similar projects
- Data pipelinesSQL Server → PostgreSQL migrationMoving a payments database to AWS, and proving the money still adds up83,892 report rows that silently stopped matching
- Data pipelinesReal-time web sessions (Flink)Live website clicks grouped into visits as they happen, with each visitor's location added5 min of quiet ends a visit
- Analytics & dashboardsContractor performance (modeled on CVS)Which maintenance contractors cost the most and miss their deadlines18% of work orders overdue, on average
Have a problem like this? Get your free AI blueprint in about a minute.
