Storing the function results

We previously implemented the result storing procedure in each function separately. In most applications, different functions will serve unrelated purposes and may call different external APIs or store the results in different data stores. In some cases, however, the functions are accessing the same data store in a similar fashion. In such cases, there may be value in implementing this procedure in a shared method to prevent code repetition. Of course, how much code can be reused and how much value the shared method may provide depends on the use case.

Let's demonstrate such a "shared" procedure for storing the data in our SQL Azure database. Keep in mind that the output binding for the table still needs to be defined in each function, but using JObject as the object type allows us to generalize a significant part of the code. We will define a common StoreOutput class to handle the data store.

Since we are treating SQL databases as an external API, this shared...