Tokyo Tyrant, AMQP (high performance). Web- hooks Your tasks can also be HTTP callbacks, enabling cross-language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross-language support, the default setting of JSON is probably your best choice. See http://json.org for than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross-language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Tokyo Tyrant, AMQP (high performance). Webhooks Your tasks can also be HTTP callbacks, enabling cross- language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross- language support, the default setting of JSON is probably your best choice. See http://json.org than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross- language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Web- hooks Your tasks can also be HTTP callbacks, enabling cross-language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross-language support, the default setting of JSON is probably your best choice. See http://json.org for than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross-language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Web- hooks Your tasks can also be HTTP callbacks, enabling cross-language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross-language support, the default setting of JSON is probably your best choice. See http://json.org for than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross-language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Webhooks Your tasks can also be HTTP callbacks, enabling cross- language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross- language support, the default setting of JSON is probably your best choice. See http://json.org than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross- language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Webhooks Your tasks can also be HTTP callbacks, enabling cross- language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross- language support, the default setting of JSON is probably your best choice. See http://json.org than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross- language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Web- hooks Your tasks can also be HTTP callbacks, enabling cross-language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross-language support, the default setting of JSON is probably your best choice. See http://json.org for than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross-language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Web- hooks Your tasks can also be HTTP callbacks, enabling cross-language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross-language support, the default setting of JSON is probably your best choice. See http://json.org for than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross-language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Webhooks Your tasks can also be HTTP callbacks, enabling cross- language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross- language support, the default setting of JSON is probably your best choice. See http://json.org than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross- language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more

Cassandra, or AMQP (message notification). Webhooks Your tasks can also be HTTP callbacks, enabling cross- language communication. Rate limiting Supports rate limiting by using the token bucket algorithm supports native binary types. However, if your data fits inside the above constraints and you need cross- language support, the default setting of JSON is probably your best choice. See http://json.org than the libraries for JSON. If you need a more expressive set of data types and need to maintain cross- language compatibility, then YAML may be a better fit than the above. See http://yaml.org/ for more