Biometric Sync Middleware Development
Budget: $250 – $750 USD
I need a compact, rock-solid middleware/API that keeps fingerprint templates in our legacy MySQL database perfectly synchronized with a fleet of new Android terminals that carry X Brand sensors. The service must pull any template changes from MySQL, push them to every terminal, and confirm successful enrollment on the device side without manual intervention.
Beyond the basic sync loop I also want:
• real-time data validation before a template leaves the server,
• detailed logging of every synchronization event, and
• smart error handling that notifies me immediately if a template fails to copy, a device is offline, or any other exception appears.
The stack is open: please propose the language and framework you believe will deliver low-latency performance and easy maintenance; I am happy to consider Python, Java, C# or anything you can justify.
Deliverables
1. Source-controlled middleware/API service with install instructions.
2. Clear schema or mapping guide showing how the MySQL tables relate to the device format.
3. README covering configuration, log locations, and notification setup.
4. Brief hand-off session where you demonstrate a live sync, an induced error, and the resulting alert.
If this sounds like your kind of challenge, let’s talk timing and milestones so we can get these terminals fully online quickly.
Beyond the basic sync loop I also want:
• real-time data validation before a template leaves the server,
• detailed logging of every synchronization event, and
• smart error handling that notifies me immediately if a template fails to copy, a device is offline, or any other exception appears.
The stack is open: please propose the language and framework you believe will deliver low-latency performance and easy maintenance; I am happy to consider Python, Java, C# or anything you can justify.
Deliverables
1. Source-controlled middleware/API service with install instructions.
2. Clear schema or mapping guide showing how the MySQL tables relate to the device format.
3. README covering configuration, log locations, and notification setup.
4. Brief hand-off session where you demonstrate a live sync, an induced error, and the resulting alert.
If this sounds like your kind of challenge, let’s talk timing and milestones so we can get these terminals fully online quickly.