Senior .NET Developer – Biometric Device Gateway & Scalable HRMS Architecture
Budget / Salary₹150,000–250,000
TypeFreelance project
LocationRemote
Posted7 hours ago
We are looking for a Senior .NET / Distributed Systems Developer to work on an existing ASP.NET Web Forms + C# + SQL Server based Biometric Attendance & HRMS application.
Currently, biometric device communication and HRMS business processing run in the same application/server environment. During high biometric device traffic, the device communication consumes excessive CPU, RAM, database connections and application resources, which can affect or shut down the complete HRMS application.
We need to separate the biometric device communication layer from the HRMS application and build an independently scalable architecture.
Target architecture:
Independent Biometric Device Gateway
Persistent TCP/IP device connections
Multiple Gateway servers with load balancing
Kafka or RabbitMQ message queue
Redis for device connection/status management
Separate data ingestion workers
Separate attendance processing workers
Secure APIs between Device Platform and HRMS
Existing ASP.NET Web Forms HRMS to remain operational
Architecture designed to scale toward 100,000+ biometric devices
The key requirement is that heavy biometric device traffic must never bring down or significantly affect the HRMS application.
We already have the existing source code and will provide it to the selected developer. The developer must first understand the existing device communication, database and attendance-processing code before implementing the separation.
This is not a new HRMS development project and not primarily a UI/web-design project. It is a backend architecture, TCP/IP, distributed systems and performance/scalability project.
The selected developer should be capable of working with existing production code and extracting/restructuring components without unnecessarily rewriting the entire application.
Must-have:
.NET
C#
ASP.NET
ASP.NET Web Forms
SQL Server
TCP/IP
Socket Programming
.NET Core / Worker Services
Multithreading / Async Programming
Distributed Systems
REST API
Message Queue
Kafka
RabbitMQ
Redis
Load Balancing
Performance Optimization
Database Optimization
Good to have:
Docker
Kubernetes
Microservices
Windows Services
Prometheus
Grafana
ELK
IoT
Biometric Devices
High-volume TCP systems
4. Most important — add screening questions
This will help you avoid hiring an ordinary ASP.NET developer.
Currently, biometric device communication and HRMS business processing run in the same application/server environment. During high biometric device traffic, the device communication consumes excessive CPU, RAM, database connections and application resources, which can affect or shut down the complete HRMS application.
We need to separate the biometric device communication layer from the HRMS application and build an independently scalable architecture.
Target architecture:
Independent Biometric Device Gateway
Persistent TCP/IP device connections
Multiple Gateway servers with load balancing
Kafka or RabbitMQ message queue
Redis for device connection/status management
Separate data ingestion workers
Separate attendance processing workers
Secure APIs between Device Platform and HRMS
Existing ASP.NET Web Forms HRMS to remain operational
Architecture designed to scale toward 100,000+ biometric devices
The key requirement is that heavy biometric device traffic must never bring down or significantly affect the HRMS application.
We already have the existing source code and will provide it to the selected developer. The developer must first understand the existing device communication, database and attendance-processing code before implementing the separation.
This is not a new HRMS development project and not primarily a UI/web-design project. It is a backend architecture, TCP/IP, distributed systems and performance/scalability project.
The selected developer should be capable of working with existing production code and extracting/restructuring components without unnecessarily rewriting the entire application.
Must-have:
.NET
C#
ASP.NET
ASP.NET Web Forms
SQL Server
TCP/IP
Socket Programming
.NET Core / Worker Services
Multithreading / Async Programming
Distributed Systems
REST API
Message Queue
Kafka
RabbitMQ
Redis
Load Balancing
Performance Optimization
Database Optimization
Good to have:
Docker
Kubernetes
Microservices
Windows Services
Prometheus
Grafana
ELK
IoT
Biometric Devices
High-volume TCP systems
4. Most important — add screening questions
This will help you avoid hiring an ordinary ASP.NET developer.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.