How should I design the architecture of a Spring Boot app?
Hi, I'm currently developing a Spring Boot application for managing incomes and expenses, and from the beginning I have a problem in designing a "clean" architecture for it.
Is the way I'm grouping code into interfaces and implementations ok, or should I pick a different approach?
I've been told on another group a while ago that my packages are too intertwined - how can I fix that? I've tried using the facade design pattern, is it enough?
Here's a link to the source code:
https://github.com/Eukon05/financetracker/tree/master/src/main/java/com/eukon05/financetracker
Thanks in advance for all replies 🙂
GitHub
financetracker/src/main/java/com/eukon05/financetracker at master ·...
A simple API for managing transactions. Contribute to Eukon05/financetracker development by creating an account on GitHub.
1 Reply
Hey, @Eukon05!
Please remember to
/close this post once your question has been answered!
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived. If your question was not answered yet, feel free to re-open this post or create a new one.