On Thu, Sep 19, 2013 at 7:13 AM, Matt <[email protected]> wrote: > It's not just convenience - master/worker communication won't scale beyond > one host. Use external storage (redis, memcached, postgres, etc).
If you are using node's cluster, you might not want to scale beyond one host, or may want to start with a single-host cluster, then move to to multi-host later. https://npmjs.org/package/strong-mq allows message queuing internally to a cluster, and then switching to external backend later, when needed, with same API. https://npmjs.org/package/strong-store-cluster allows key/value store internal to a cluster, you may find it useful (we are planning on extending across other key/value stores when we have time, as strong-mq does). If you are specifically using connect/express with cluster, you may find this useful (build over the above two): https://npmjs.org/package/strong-cluster-connect-store If you are interested in looking at this approach, you can find some tutorials and docs up here: http://docs.strongloop.com/strongnode/#getting-started-with-strong-store-for-cluster Cheers, Sam -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
