Simulating a persistent backend

Hoverfly Cloud supports two distinct mechanisms for simulating a persistent backend. Data sources, and Journal templating. Both of them depend on templating.

CSV Data sources

You can upload up to 5 CSV files as data sources when editing your simulation from the Simulation tab.

This is configured at the simulation level, and the ability to store and retrieve tabular data within this data store is scoped at the service instance level.

You can both query data from a CSV data source as well as manipulate data within a data source by adding to it and deleting from it. Hoverfly supports a number of templating methods for simple read, update and delete functions. In addition Hoverfly supports a templating function that allows simple SQL like commands for SELECT, UPDATE and DELETE.

This is only available to enterprise customers.

You can read about this approach here

Journal Templating

Hoverfly Cloud has the ability to retrieve from memory any past request that has been indexed with a key you provide, and then retrieve any part of that request or response for processing in your current response.

This is configured at the service instance level, and the ability to store and retrieve historical requests and responses is scoped at the service instance level.

This ability to look up in history, is one of the ways Hoverfly supports the mocking of a persistent back-end service. This is only available to enterprise customers.

You can read about this approach here