BioID Web Service Deployment Scenarios

event_note December 17, 2012

Today we will describe three common deployment scenarios of the cloud-based BioID Web Service (BWS). The BWS depicted in the diagrams are the instances of our BioID Web Service on Microsoft Windows Azure. The Customer is using the BioID Web Service to enhance his product with biometrics and the Client is the end-user accessing the customer’s offering. 

Cloud to Cloud

BWS Cloud to Cloud

This is probably the most common scenario for a BioID Web Service integration: The BWS is deployed at one cloud service provider, i.e. Microsoft Windows Azure and the customer utilizes a different cloud service provider. This is the implementation often seen by rather new service implementations which already utilize cloud computing but now are to be enhanced with biometrics like face detection, face recognition or voice recognition.

Common Cloud

BWS Common Cloud

If the integration of the BioID Web Service is already included in planning of new system deployments following scenario has certain benefits: The newly developed service is deployed at the same cloud service provider as the BWS. Ideally in the same region or even better in the same data centers. This reduces communication costs and cuts down network latency.

Perimeter to Cloud

BWS Perimeter to Cloud

A third option would be to use the virtual private network (VPN) offering of your cloud service provider. This may be a good scenario for extending already deployed systems with biometrics. On one hand it would allow for storing sensitive data on the in-house infrastructure of the customer and securely access the biometric services of BWS. On the other hand the BioID Web Service is deployed in a standard implementation and still offers all benefits of cloud based services.