tanspring

Problem

A portfolio backend sounds like CRUD until the domain shows up. Skills nest inside categories, career entries link to organisations, and every one of them needs consistent errors, versioning and an auth story that is not bolted on afterwards.

Approach

Spring Boot with JPA and Hibernate over the full domain, and generic controller and service templates so a new entity is a subclass rather than another copy of the same fifty lines. JWT with role-based authorization, a global exception handler mapping domain failures onto REST error shapes, optimistic locking through a shared base entity, and springdoc publishing OpenAPI from the code.

Outcome

• 323 files over 40 commits, the deepest public Java codebase of the set.
• Runs from a single docker-compose command, database included.
• Domain coverage reaching skills, organisations, academics, achievements, certificates, experience, volunteering and social links.