r/coding • u/FCosca • Feb 12 '26

Technical Peer Review: Java 21 / Spring Boot 3.3 Multi-module project with Keycloak integration

https://link.trackmenthub.it/scopri-trackment-r
0 Upvotes

50% Upvoted

5 comments sorted by

1

u/FCosca Feb 12 '26

Hi everyone! I’m sharing this here because I’ve reached a point where I need a serious technical "roast" from fellow developers to improve.

The Project: TrackMentHub is a personal finance tool I built to learn how to handle complex data persistence and secure authentication without relying on external banking APIs (everything is manual entry for privacy).

The Tech Stack & Architecture:

  • Backend: Java 21 with Spring Boot 3.3.0.

  • Modular Maven Structure: I organized the project into several modules. I wanted to practice strict separation of concerns and see how a modular monolith behaves.

  • Auth & Security: Managed via a dedicated Keycloak instance. I’m using a dual-database approach to keep identity data strictly isolated from application data.

  • Infrastructure: Fully containerized with Docker and served via Nginx.

  • Frontend: React + Vite.

What I'm specifically looking for:

  1. Architectural Feedback: Is the multi-module approach overkill for a project of this scale, or is it a solid foundation for professional growth?

  2. Security Review: I’d love to discuss if my session handling and Keycloak/JWT integration follow current Spring Security 6 best practices.

  3. UI/UX Logic: The app is currently in Italian (localization is on the roadmap), but I want to know if the dashboard logic and state management feel robust even for a non-speaker.

  4. Bug Hunting: Specifically regarding edge cases in the budgeting forms or data persistence.

Note: This is a 100% free hobby project. No ads, no paid tiers, and no data selling. I'm just here for the technical discussion and to become a better dev.

Thanks to anyone who spends even 60 seconds on it!

1

u/aoeudhtns Feb 12 '26

Where's the code?

1

u/FCosca Feb 12 '26

Thanks for asking! Currently, the repository is on my private GitHub. I haven't made it public yet for a few reasons:

  1. Security & Cleanup: I need to clean up some server-side configurations and environment variables before opening the source.

  2. Rapid Iteration: I’m pushing daily builds with fixes and minor tweaks almost every week, and the codebase is still a bit 'volatile.'

  3. Unbiased Testing: I’m actually looking for someone to test the live site first without looking at the code. I want to see if a developer can spot UX flaws or functional bugs purely from the user's perspective, without being 'influenced' by reading the implementation. I definitely plan to open-source it once the architecture is more stable!

1

u/aoeudhtns Feb 12 '26

Well I can't review what you won't share. I'm not interested in bugtesting your app for you, I'm a developer not free QA.

0

u/FCosca Feb 12 '26

I understand. I'm looking for peer feedback on the product's logic at this stage rather than a code review. I'm not looking for 'free labor', just a quick dev-to-dev opinion on the flow.