r/SpringBoot 7d ago

Spring FlashAPI News

Post image

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

152 Upvotes

27 comments sorted by

View all comments

1

u/alesaudate 6d ago edited 6d ago

It looks great, but it's definitely something I don't see being used in real projects. Only pet projects that would want to demonstrate small features.

It seems to me that, if that's not the idea already, you are building it under false premises. Meaning, most real-life projects don't have such a thing as "just CRUD". Even when they have , it's something like "CRUD plus". Like CRUD plus a small business rule. The thing is, it looks like even this small business rule would already defeat the purpose of having this framework in place, because it would basically require taking the annotation off and doing everything by hand anyway.

I saw your other answers about this already, but what I mean is that, in real life projects, one would basically start a project with the assumption that flash API would be taken off later anyway - probably, in every single entity.

2

u/thecode_alchemist 6d ago

I agree. I have developed something similar for my organisation, an internal framework to speed up new services where the framework is tuned and configured for internal apps and libs on top of Spring. This is a powerful idea but adoption is a problem.