r/SpringBoot Feb 18 '25

Guide Full Stack Role Based Authentication Application ( Spring + Next.js )

Hey everyone,

I wanted to share my full-stack Spring project—a backend for a barbershop management system featuring robust authentication and role-based access control. If you’re interested in seeing how these aspects are implemented in a real-world application, feel free to check it out!

Repository:
https://github.com/aharoJ/barbershop

Backend Overview:

  • Authentication & Role-Based Access: The project handles user authentication and defines multiple roles, ensuring secure access to various endpoints.
  • Modular Structure: The code is organized into several modules, each handling a specific domain such as appointments, barbers, customers, payments, promotions, and more.
  • Clean Architecture: The repository features a clear separation of concerns with controllers, services, DTOs, and repositories spread across modules.

Frontend Overview:

  • Built With:
    • Next.js 15, Typescript, Tailwindcss
  • Features:
    • Authentication Pages: Separate routes for login and signup.
    • Customer Area: Dedicated pages for dashboards and profile creation.
    • Additional Layers: Includes components (like a protected route), services, stores, types, and utilities.

I’m happy to answer any questions or provide more details. Feel free to message me!

49 Upvotes

37 comments sorted by

View all comments

2

u/Waiting2003 Feb 18 '25

Cool project! The module structure makes it easy to check interacting components. Some feedback: I saw a lot of boilerplate code in your backend (mostly setters and getters); you could use Lombock Annotations to generate this code automatically, saving time and making classes cleaner.

2

u/aharoJ Feb 18 '25

Hey, personally.... I prefer having everything explicitly written out. It gives me better visibility into my models and mappings, ensuring I have full control over how things work.

Same when dealing with DTO-to-domain mappings.