Operational Considerations

Saving Data

The application will save data produced from the observations passed in. Upon restart, the system resumes with all data available from a prior session. So the underlying model created from past observations will be preserved across system restarts, if the underlying file system is restored.

A set of administrative API endpoints are included in the built-in documentation. To clear out all data from all contexts and restore an instance of the running application to the empty state it began with, you can use the POST /api/v1/admin/reset API endpoint.

For alternative options for data storage, high availability, clustered operation, and alternate data storage formats, please contact thatDot’s sales team.

Shutting Down

To shut down the system cleanly and ensure that all data is property persisted, the API endpoint at POST /api/v1/admin/shutdown is provided. Please be sure to call this API and await a successful response before shutting down the application or container. Failure to properly shut down the system can result in loss of data.

System Sizing

thatDot Novelty Detector can run in a container or on a full host machine. Custom deployment configurations (e.g. on-premise deployment, non-containerized deployments, alternate storage configurations, etc.) are available upon request. Performance is primarily measured as throughput of the number of observations per second. A system the size/scale of a modern laptop (with SSD) will often witness throughput around 20,000 observations per second. Increasing CPU and RAM will allow for higher throughput, though the total throughput is limited by several other considerations, including the parallelism query parameter in the observe and observe/bulk API endpoints.