v0.1.0 – Quantum Plan & Dual Backends

v0.1.0 — Quantum Plan & Dual Backends

TL;DR: End-to-end Explain Plan, dual backends (LOCAL / QUANTUM via Qiskit), hardened Python runner, consistent API, tests, and clearer docs.

Highlights

• End-to-end Explain Plan (domain → application → infrastructure → web)
• Dual backends: LOCAL and QUANTUM (Qiskit; simulator or real hardware via config)
• Hardened Python runner: JSON stdout contract, exit-code handling, sane timeouts
• Consistent API: stable DTOs + global exception handler (uniform error envelope)
• Tests & DX: service/web layer tests, clearer README, dedicated local profile

What is “Quantum Plan”?

A compact, machine-readable plan that describes how a query executes on the quantum path:

• Backend selection (HW/simulator) and run parameters (e.g., shots)
• Algorithm choice (e.g., Grover) and expected iteration count
• Logical mapping query → circuit/calls
• Complexity/cost hints
• Dry-run preview to validate the pipeline before real execution

Requirements

• Java 17+, Maven
• (Optional) Python 3.10+ with qiskit, numpy

Known limitations

• Integration test that executes the Python path (mock script) — planned
• Docker hardening (multi-stage, non-root) — queued
• Qiskit backend defaults may evolve after benchmarks

Roadmap

• Runner hard timeouts & resource caps
• Swagger examples for LOCAL/QUANTUM
• Tests for non-JSON/timeout/exit≠0 paths
• Docker multi-stage & non-root user

---

Links: repo — https://github.com/swampus/plank-db ·

#Java #SpringBoot #CleanArchitecture #DSL #Compiler #SystemsDesign #OpenSource #Quantum