To retrieve data from a JSON document, the response type must be set to JSON.Here’s a simple example of a JSON response: To access the foo property in a response mapping, we can just use the name of the property since it is in the first level of the JSON object, foo.Each Webhook may have an unlimited number of response mappings, which are added and edited by clicking the Edit button in the Response Mappings pane of your Webhook: Response Mappings are created via a pairing of a Response Attribute, which is a path to the desired property in the XML or JSON document, and the Marketo Field, which specifies the Lead field which will have the value written to it from the Response Attribute.JSON properties are accessed just as you would in Javascript, with dot-notation.Specifically the Elastic Search order index contains additional details for the So this is going to make the ORM query against the DB more expensive because now we join to customer, order details and products.

You can use the value returned from data Source Key as a unique identifier for publishing data into the data source.

For Postgres I did add indexes on order date and status but other wise kept with defaults for both Postgres and Elastic Search.

This is not about getting the best numbers but instead looking at the variations we can see in changing selectivity of predicates and denormalisation.

It is also interesting to note that for Elastic Search this is a non-scoring query (filter query only) so it's good to see how it compares ballpark wise to Postgres for this simple query.

Elastic Search did very well but actually the object it returned contained some additional denormalised information that we didn't have in the Postgres query.