On Tue, Nov 5, 2013 at 3:34 AM, stephanos <[email protected]> wrote:
> I want to split my big Java application into multiple smaller modules. > They will not be 100% independent so they will need to communicate with > another. > > I'm wondering... > > - what communication protocol to use? > - will latency be low enough? are there spikes? > > What kind of latency numbers are you looking for? Do you need real-time communications, or can the communication be done async/with a bit of lag? If you need realtime communication with a different module, you can design a simple API and urlfetch to that. XMPP can also be used for fast communication. If you can tolerate a delay or do the work async, you can communicate between different modules using task queues. Depending on your application's architecture, you can also try refactoring your application so shared services are consolidated into shared libraries. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
