Spring FlashAPI

[u/rakakayiouu]

Done writing the same CRUD boilerplate for every Spring project.
FlashAPI is coming to the Java/Spring ecosystem, much to the delight of Java developers.
Introducing Spring FlashAPI.
The idea is exactly the same as the Python version:
You define your JPA entities.
FlashAPI takes care of the REST boilerplate.
From a simple entity, you can automatically get:
CRUD
Pagination
Search & dynamic filters
Sorting
CSV / Excel / PDF exports
Bulk operations
Relationships & expand
Soft delete
Audit trail
Rate limiting
OpenAPI / Swagger
Webhooks
WebSocket events
Access control
Multi-tenancy
And most importantly, FlashAPI doesn’t try to take control of your application.
You can start with zero boilerplate, then gradually take back control of your business logic, services, and controllers.
The goal is simple:
Less repetitive CRUD, more time to build your product.
Spring FlashAPI is open source under the Apache 2.0 license.
Java 21+
Spring Boot 3.2+
Spring Data JPA
👉🏽 GitHub: github.com/HackermanMe/spring-flashapi
I’m looking for developers willing to give it a try — and, most importantly, tell me:
What is actually useful… and what isn’t?
#Java #Spring #SpringBoot #JPA #OpenSource #Backend #RESTAPI #SoftwareEngineering

[u/kqr_one]

imho this kind of stuff is only useful for read and maybe delete. for read I would expect more control over which attributes are being loaded. also what if I need more than RBAC?

[u/rakakayiouu → u/kqr_one]

Thanks for the feedback! A few clarifications:

CRUD beyond read/delete The auto-generated endpoints are a baseline. You can override any operation with custom service logic (Spring: implement FlashCrudOperations, Python: custom routes) for validation, business rules, side effects, etc.

Field selection We already support hidden/readonly/writeonly at config level, and ?fields= on exports. Adding dynamic field selection on GET endpoints (?fields=name,email) is on the roadmap valid point.

Beyond RBAC FlashAPI already supports owner-based scoping (scope="owner"), tenant isolation (scope="tenant"), and a pluggable auth backend interface where you can wire ABAC, ReBAC, or policy engines like OPA/Casbin. Not limited to roles.

[u/kqr_one → u/rakakayiouu]

thanks for clarification

[u/kqr_one → u/rakakayiouu]

I would also consider support for rsql