We're passing around lots of small chunks of json. For example, user accounts are handled within there own API, so a registration server will take the form data, package it up and send it via rest to the accounts server to create the user.
Sent from my iPhone On 29/10/2011, at 3:24 PM, Chris Berkhout <[email protected]> wrote: > Yeah, it does depend on your application. What kind of communication > do you need? I wonder if it's something that you can avoid > implementing your own interface for (e.g. maybe the filsystem, or > shell commands via ssh, or database replication would fit better). > > If you need for your own interface for message passing or similar, > HTTP is probably a good choice. > > ElasticSearch has a JSON REST API, and I like it a lot. You get > advantages like being able to log in curl format and cut and paste > from there back into the terminal for debugging. > > CouchDB is another good example. > > I'd say do it, unless you really know that you're going to have a > performance issue. Premature optimisation is the root of all evil. > > Cheers, > Chris > > > On Sat, Oct 29, 2011 at 12:07 PM, Ivan Vanderbyl > <[email protected]> wrote: >> Hi Sam, >> It depends on what sort of communication you are doing, if it is just >> events, messages etc it might be worth checking out ZeroMQ or AMQP. >> That said, I have apps which use HTTP for the above just because consuming >> the messages is made a lot easier if you already have a HTTP stack, e.g. one >> serving a rails app. >> – Ivan >> On 29/10/2011, at 2:56 PM, Samuel Richardson wrote: >> >> What are peoples thoughts on using rest for internal communications between >> servers? Is there too much overhead setting up HTTP connections? too >> verbose? >> Samuel Richardson >> www.richardson.co.nz | 0405 472 748 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" 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/rails-oceania?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" 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/rails-oceania?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
