Publishing messages

Publishing messages with Sneakers is left open to interpretation. Why?

Flexibility

Sneakers will not lock you into a message structure, and it will not magically hide serializing (and deserializing) objects from you - which is what traditional background processing frameworks like Sidekiq, Resque and DelayedJob do.

• Use your own message format, and pack only what you need into a message, maintain backwards compatibility as you see best.
• Use your own publishers - in any language or platform. We currrently use Node.js and Go in order to publish messages - which has huge advantages over keeping an order of magnitude more Ruby services to keep with the scale.

Performance

Not only are you not locked-in to how a message looks - you're also not locked to a format. You can push a JSON serialized object, custom text serialized object, binary, msgpack, protocolbuffers, or what have you.

You can also pick the best serialization format that performs best to your workload.

This page originated from the following issue discussions

• https://github.com/jondot/sneakers/issues/6
• https://github.com/jondot/sneakers/issues/137