GoHealthy – Healthy Lifestyle Application
2024 · Backend Developer (team of 6)
The problem
GoHealthy helps people keep healthy routines: scheduling activities, logging meals, and setting medication reminders. All of that leans on a backend that stores the right data and for reminders especially the right times.
What I built
- I was the only one on the backend (team of six). I designed a seven-table schema and built a Spring Boot REST API 26 endpoints covering auth with roles, activity and medication schedules, meal logging, and motivational content, organized in clean controller–service–repository layers. I added a scheduled job to send reminders at the right time, and I wrote unit tests for the service layer.
The stack
The result
- The interesting part was a deployment bug two things at once. The API's CORS setup only allowed the localhost dev origin, so the client's requests were blocked until the backend was deployed with the right allowed origin. And schedule times were coming out wrong, which turned out to be a timezone mismatch fixed by syncing the time on the deployment server. Once both were sorted, reminders fired at the right time again.
backend