Hey devs!
I’m working on a project to develop an employee management system with multi-location support and key features like certification tracking, custom reporting, and a dashboard for staff management. The goal is to build something scalable and secure, capable of growing with the organization without a complete rebuild.
I’d love some feedback and insights from the community, especially those with experience in building similar systems. Here’s a breakdown of the requirements and considerations:
Features to Include:
Employee Profiles: Full profile with attributes like certifications, traits, and evaluation history.
Certification Tracking: Track and manage certifications like CPR, First Aid, etc.
Dashboard & Reporting: Provide real-time reporting and analytics on staffing, certifications, and employee performance.
Multi-location Support: Manage staffing across multiple locations, with filtering by location.
Security: The system will be deployed behind Tailscale for private access; what’s the best way to secure it?
Tech Stack Considerations:
Database & Backend Framework: What databases and backend frameworks do you recommend for scalability and flexibility?
Security: Given the private system setup (Tailscale), what would be your approach to ensuring security without compromising ease of access?
Growth: How would you design the system for future expansion (e.g., adding new locations, new certifications)?
What I’m Looking For:
Your experience building similar systems
Recommendations for the best tech stack to handle these features
Security advice, especially for private systems behind Tailscale
Thoughts on ensuring scalability without a full rebuild down the line
I’m aiming for a long-term project that can adapt and grow with the business, so any advice on future-proofing the system will be highly appreciated.
Feel free to drop your thoughts, ideas, or any similar projects you’ve worked on!
Let’s build something amazing!
Top comments (1)
the multi-location angle is where it gets tricky. one thing that trips people up is deciding whether location is part of the entity identity or just metadata. if you treat it as identity, you end up with different record IDs for the same employee in different regions and syncing gets painful. if it's metadata, you need to be careful about what happens when an employee transfers locations mid-payroll cycle. curious how you're handling that transition case in your design.