Hi everyone,
I’m a full-stack developer working mainly with Spring and React, and over the past few months I’ve been building something that I think could change how we generate backend applications.
The idea came from a simple frustration: AI is great for generating code, but when it comes to real projects, especially backend systems, things quickly become inconsistent, hard to maintain, and dependent on prompts that change every time.
Even for simple CRUD applications, I found myself spending too much time:
- Tweaking prompts
- Fixing inconsistent architecture
- Cleaning up generated code
- Rewriting things I’ve already built many times before
So I started building a different approach.
Instead of relying on AI for code generation, I’m building a config-first deterministic code generator.
How it works
You start by running a simple command inside your project. Then you choose your stack and setup.
After that, the tool generates a full project based on your choices.
It supports configuration files like:
architecture.ymldatabase.ymlendpoints.ymlauth.yml
From there, you define your system using configuration:
- API endpoints (
GET,POST,PUT,DELETE) - Pagination rules
- Exception handling strategies
- Authentication and security rules
- Mapping strategies (DTOs, etc.)
And the generator produces a full backend codebase.
What it currently supports
Right now, the project is focused on backend generation, and it is currently Spring-based. It already includes:
- Multiple architecture styles
- Different design patterns
- Endpoint structure variations
- Exception handling strategies
- Database migrations with Flyway
- Mapping with MapStruct
- Clean project structure generation
What I’m still figuring out
I’m still at an early stage, and I’m not fully sure about the right direction for scope and design.
For example:
- Should the tool stay highly opinionated or support many architectures from the start?
- How flexible should the configuration system be?
- What is the right balance between power and simplicity?
I’m also trying to understand how people would validate something like this in real-world usage.
Why I’m sharing this
I’m not building this only for Spring, and I don’t want it to be limited to one ecosystem.
The goal is to make it extensible across different stacks and use cases over time.
Right now, I’m mainly looking for:
- Honest feedback on the idea
- Real-world opinions from developers
- Suggestions on architecture and design decisions
- People who might want to collaborate on the project
If you find this interesting and want to contribute or collaborate, feel free to reach out. I’d genuinely love to build this with other developers who care about clean architecture and developer experience.
And even if you don’t want to collaborate, I’d really appreciate your thoughts and criticism 🙏
Top comments (0)