HR Platform
Building modular software for workforce operations
The problem
The problem
Employee records, payroll and access permissions often end up spread across spreadsheets and HR software that wasn't built around how a specific organization actually works, with no clean way to extend or connect them to other internal tools.
The approach
A microservices architecture splits the platform into separate Auth, Employee and Payroll services, each with its own PostgreSQL database, communicating through a RabbitMQ event bus. Redis holds a shared permission cache so authorization checks don't need a round trip to the auth service on every request. A React admin frontend sits on top, and Docker Compose orchestrates the whole stack locally with seed and reset scripts.
Implementation
Implemented
- Auth service: users, roles, permissions, JWT-based authentication
- Employee service: employees, departments, positions
- Payroll service: salaries, payroll records
- React admin frontend
- Docker Compose orchestration with seed/reset scripts
Not yet built
- Time and attendance tracking (in progress)
- Audit logging (in progress)
Engineering decisions
Engineering decisions
A database per service
Each service owns its own PostgreSQL database rather than sharing one schema, so services can change independently instead of coordinating every migration across the whole platform.
Events over direct calls between services
Services communicate through RabbitMQ rather than calling each other's APIs directly, so an employee-record change can trigger downstream payroll updates without the employee service needing to know payroll exists.
A shared cache for authorization
Permission checks read from a shared Redis cache instead of hitting the auth service on every request, keeping authorization fast without duplicating the permission model into every service.
Results and status
Results and status
This is an independent engineering project, not a system in production use — it hasn't been deployed at an organization or handled real employee data. What's verified is the architecture itself: three working services with a real event-driven integration between them, not just a design document.
Contributors & attribution
Contributors and attribution
Built by Elijah Soladoye.
Have a similar operational challenge?
Tell us what's happening and we'll tell you honestly whether it's something we can help with.