Unfortunately every fingerprint reader outputs a unique hash per fingerprint, which is why if you break it you can loose all of your data. So even with a thiefs hash's you'd still need the thief to prove it was them.
I'm being a bit pedantic about the "every fingerprint reader" mention and am assuming that mention also includes non-Apple devices. HTC and Samsung phones have, in the past, stored fingerprint images in an accessible location. What's worse was that the fingerprint image would be refreshed with every swipe/finger touch!
I dislike Microsoft in general, but I believe you can accomplish this with SQL server easier than other SQL databases. SQL CLR and your own defined types. Maybe you could even go as far as using some dynamic types with ExpandoObject to have fully dynamic lamda expressions on the columns, however I dont know how well this would perform.
On my Apple Airport Extreme with 2 additional Airport Expresses and Cat6e from modem to main Airport unit, on Wifi I'm getting about 820Mbps. So wifi, with the right equipment is fine. At first I was skeptical that Apple's wifi hardware was any good, but after just 3 weeks I'm sold.
It is great if you're not experiencing the problems we are.
If you use AWS services besides S3 it can get very tricky to not overwhelm your egress and not suffer performance issues. Scaling this configuration in an elastic way is certainly not turnkey in the current VPC environment, and probably won't be until Amazon finishes something like the S3 gateway for them.
Make a dockerfile, make sure it works and you understand it. Then go into Elastic Beanstalk and click new application and there is an option for loading a dockerfile, boom. For you this may work, for me it's more complex.
