[j42]

Can you tell me where I may find more info on KDB or how this may compare to more traditional serving options for static resources, HLLs or anything that might fit well in a large tree.

I'm trying to understand exactly what its limitations are though, both in terms of what it can do and when it may be a poor candidate (when lower req/s is ok and greater flexibility is needed).

[geocar]

In kdb, GET requests are normally mapped to .z.ph[1] which synchronously returns the HTTP response. dash supports this as well (sync mode) when it doesn't understand the query string parameters, and then dash works just like a faster .z.ph for KDB.

Async mode is designed when dash knows what the HTTP response will be and can send it immediately. It then relies on kernel queueing to send the same message to kdb which allows for logging (or other processing, like HLL or anything else). This gives a significant performance boost so it's worth optimising.

[1]: http://code.kx.com/wiki/Reference/dotzdotph