y9dssb2b77-maker / enajenarteAA2

What is enajenarteAA2?

enajenarteAA2 is a Java REST API built with Spring Boot for managing an emotional health company that organizes events and workshops. It handles five core entities: events, speakers, workshops, users, and registrations. The API exposes standard CRUD endpoints for each, with the workshop entity demonstrating API versioning -- the original endpoints remain at `/workshops` while a v2 version adds client-optimized responses with speaker names and capacity data, duplicate detection, and conflict handling for workshop deletion when registrations exist. The project includes Docker containerization, environment-separated configurations for local development versus production, and automated integration tests running through GitHub Actions on every pull request.

Why is it gaining traction?

The standout feature here is the API versioning approach using workshops as a practical example rather than a contrived demo. Each version demonstrates real business logic: v2 transforms internal speaker IDs into readable names, exposes capacity limits for client display, and prevents accidentally deleting workshops that have active registrations by returning 409 conflicts. Beyond versioning, the project shows production-ready practices including environment-specific database connections through Docker Compose, GitHub Actions pipelines that spin up containers, run Newman test collections, and tear down automatically, and AWS EC2 deployment documentation that walks through Security Group configuration and public IP access. The 144 unit tests combined with Newman integration tests provide confidence in changes before merging.

Who should use this?

This is primarily an academic exercise for students working on data access coursework. Java developers learning Spring Boot would benefit from examining the layered architecture separating controllers, services, and repositories. Teams evaluating API versioning strategies could reference how the workshop version demonstrates versioning conventions with proper conflict responses and backwards compatibility. Anyone building similar health-focused event platforms would find the domain model with speakers, workshops, and user registrations a reasonable starting structure to extend.

Verdict

With only 19 stars and an academic focus, this project shows solid engineering practices but represents course work rather than production-ready software. The ~0.9% credibility score reflects its early stage -- the extensive documentation and test coverage demonstrate capability, but I would want to see active maintenance and production adoption before recommending it for critical systems.