Secure Data Management API
Budget: ₹1,250 – ₹2,500 INR
I’m looking for a seasoned Java/Spring specialist to create a production-ready REST API with Spring Boot, and the very first milestone is clear: build the core service from the ground up.
Scope
• Secure every endpoint with JWT-based user authentication and role-based authorization through Spring Security.
• Provide full CRUD data retrieval and management backed by JPA/Hibernate (PostgreSQL is my default, but keep it abstracted for easy swap).
• Wire the API to at least one external third-party service; I’ll supply the specific service and credentials once we start.
Deliverables
1. Well-structured Spring Boot 3.x project in a Git repository.
2. Dockerfile + docker-compose.yml so I can spin it up with a single command.
3. README covering build, run, and test instructions.
4. Unit and integration tests (JUnit 5, Testcontainers where helpful) showing ≥80 % line coverage.
5. Postman or OpenAPI/Swagger collection that documents every public endpoint.
Acceptance Criteria
• Successful JWT login returns a signed token; protected routes reject invalid or missing tokens.
• CRUD endpoints persist and retrieve data accurately in the relational database.
• Third-party integration responds with real data and graceful fallbacks on failure.
• All tests pass via `mvn test` (or `gradle test`) inside the container.
Once this API is merged to main, we’ll discuss optional follow-ups such as AWS deployment and ongoing bug fixes, but the focus right now is the robust API itself. If this sounds like your wheelhouse, tell me briefly how you’d tackle the JWT layer and any previous integrations you’ve handled—then let’s get started.
Scope
• Secure every endpoint with JWT-based user authentication and role-based authorization through Spring Security.
• Provide full CRUD data retrieval and management backed by JPA/Hibernate (PostgreSQL is my default, but keep it abstracted for easy swap).
• Wire the API to at least one external third-party service; I’ll supply the specific service and credentials once we start.
Deliverables
1. Well-structured Spring Boot 3.x project in a Git repository.
2. Dockerfile + docker-compose.yml so I can spin it up with a single command.
3. README covering build, run, and test instructions.
4. Unit and integration tests (JUnit 5, Testcontainers where helpful) showing ≥80 % line coverage.
5. Postman or OpenAPI/Swagger collection that documents every public endpoint.
Acceptance Criteria
• Successful JWT login returns a signed token; protected routes reject invalid or missing tokens.
• CRUD endpoints persist and retrieve data accurately in the relational database.
• Third-party integration responds with real data and graceful fallbacks on failure.
• All tests pass via `mvn test` (or `gradle test`) inside the container.
Once this API is merged to main, we’ll discuss optional follow-ups such as AWS deployment and ongoing bug fixes, but the focus right now is the robust API itself. If this sounds like your wheelhouse, tell me briefly how you’d tackle the JWT layer and any previous integrations you’ve handled—then let’s get started.