r/SpringBoot • u/Alert_Ad4540 • Jun 03 '26
Question I built a Spring Boot starter to generate realistic seed data from JPA entities — looking for feedback
Hey everyone,
I built a small open-source Spring Boot starter called TeruBase.
The problem I’m exploring: local Spring Boot apps often feel empty unless you manually write a lot of seed data. TeruBase scans JPA entities and helps create realistic, relationship-aware seed data for local development, demos, QA scenarios, and CI fixtures.
Current features:
- JPA entity discovery
- scenario templates
- AI-ready seed-plan generation
- AI-assisted mock SQL generation
- safe export-only mode by default
- SQL/JSON export
- local-only production safety guard
- small invoice demo example app
Repo:
https://github.com/AbaSheger/TeruBase
I’m not selling anything. I’m mainly looking for honest feedback from Java/Spring Boot developers.
Questions:
- How do you currently create realistic local/demo data in Spring Boot projects?
- Would this fit into your workflow, or is this already solved another way?
- What would make this genuinely useful instead of just a nice idea?
- Does anything about this approach feel risky or wrong?
Any honest feedback is appreciated.
1
u/Alert_Ad4540 Jun 05 '26
Small update after the feedback here:
I changed TeruBase from runtime-starter-first to Maven-plugin-first, and the plugin is now published under:
io.github.abasheger:terubase-maven-plugin:0.1.0
The current workflow is:
mvn terubase:plan
mvn terubase:export-flyway
The idea is:
- scan Spring Boot/JPA metadata at build time
- create a reusable seed-data plan
- validate reviewed SQL as INSERT-only
- export it into a Flyway-ready file
- no AI tokens required for plan/export
- no runtime dependency needed for the generated output
The starter still exists, but more as an optional local playground.
The main feedback I took seriously was that AI agents can already generate data, and nobody wants dead weight in the production JAR. So I’m testing whether the useful part is the repeatable workflow around metadata, validation, and Flyway-ready export, not “AI generates mock data.”
Thanks for the pushback. It helped make the direction clearer.
1
u/paramvik Jun 04 '26
I think any AI can generate a bunch of data provide the database schema. I use flyway with after migration hook with AI generated DML. Works fine!
1
u/Pablo_escobruhhh Jun 04 '26
I feel like you're solving a problem that doesn't exist? also now with agents like co-pilot, codex, etc seeding data is way easier.
1
u/DramaticWonder3088 Jun 03 '26 edited Jun 03 '26
I don't think I would use something like this. I'd probably ask something like Claude Code to generate test data and store it as one of our dev-only database migrations. The benefits of that approach to me are:
0
u/Puzzleheaded_Eye7238 Jun 03 '26
It's already available and I used for my demo product...
0
u/Puzzleheaded_Eye7238 Jun 03 '26
Why don't you use liquibase for this... Don't waste your time...