~/talk

Building reporting services using Quarkus and AI

links:none on file
slides:none on file

Built a Quarkus middleware that exposes a simple users/orders API, uses Quarkus Dev Services + Postgres and import.sql for data, and plugs LLMs (local AMA/Llama3 plus OpenAI GPT‑4o) to translate natural‑language requests into SQL on the fly. The pipeline includes an LLM-to-SQL translator (prompted with schema, examples and retry logic) and an optional sensitive-field scrubber that calls a second model before returning results. It mostly works — some queries need reprompting, guardrails validate results, and the scrubber adds latency but successfully removes passwords.

AI-written summary · about

  1. 0:00AI-powered reporting services
  2. 3:57Why Quarkus
  3. 7:08AI integration with LLMs
  4. 10:00Java models via AI prompts
  5. 15:16Sample data with AI
  6. 18:26Quarkus with PostgreSQL
  7. 20:13Dynamic SQL from natural language
  8. 25:17Testing AI queries
  9. 31:03Securing API with AI filtering
  10. 33:35Quarkus guardrails
  11. 35:25Future vision
  12. 39:05Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.