As a Partner that wants to focus on application logic instead of writing a database, I often receive manual data inputs, results of time-series calculations, and create predictive data sets that require persistence SO THAT our application can receive and publish data from OSIsoft and other sources without the overhead of managing a full stack of software.

Ideally this local historian would seamlessly integrate with our application without having to directly embed it (so upgrades are easy) - while also having a high affinity to Data Sharing behaviors in OSIsoft's Cloud Services (thus making it near zero configuration).

Some of our applications require us to use historian-like features in a stateless manner, and other applications require us to persist data like a rolling buffer in case a service recycles or between calculation intervals.