FaceTec Server - Storing API Requests & Responses
Learn about important considerations for Data Storage, Logging API Requests, and storing data that is inputted and generated by FaceTec SDKs.
Data Storage Strategy
A comprehensive Data Storage Strategy is important for a variety of reasons:
- Cost
- Privacy & Security
- Storage Size & Data Deletion
- Investigating Unexpected Behaviors
You and Your Team have 100% control over all parts of Data Storage and Deletion, including what type of Data is stored, how long this Data is stored, and when this Data should be deleted.
The decisions behind implementing your Data Storage Strategy are entirely yours, according to your requirements.
For additional aspects to consider, please see the Reviewing & Altering Data Storage in Your Architecture Guide.
API Request Logging
FaceTec recommends adopting a strategy that places a minimal burden on your System Architecture, while allowing for healthy oversight of the most recent API Requests. A common strategy employed by many of our Customers and Partners is to log and store the last 30 days of Raw API Requests to any of a wide variety of cheap data storage solutions. This will allow you to trace any behaviors in the event of an unexpected behavior in your business logic or behavior that you believe to be a problem with the FaceTec Software.
Important Note: MongoDB JSON data or String Outputs from the FaceTec Servers are not sufficient for most investigations by You or by FaceTec. In most cases, the original request sent io the FaceTec Server is needed for both you and FaceTec to investigate the behavior.