River is basically an infrastructure for building service oriented systems.
What can you build with a service oriented system? Pretty much anything. So what would the "most appealing use cases" be? Anything. Some things it does more naturally than others: Works well in Java, less so with other languages. Of course that doesn't preclude doing a non-Java front end and having it talk to Java and Jini services at the back via RESTful interfaces and such. There are also some other means (Surrogate) for working around this problem. It has a nice dynamic lookup mechanism so long as you have multicast available in your networks. The likes of Amazon and Google do, for some reason many smaller concerns don't. A standard 3-tier architecture with display, business logic and shared database storage really doesn't fit well but then it wouldn't qualify as an SOA so no surprise. If you have something more specific in mind, I can give you more specific commentary but your question is so generic, so open, writing anything with detail beyond the most superficial is impossible. Kinda like "What's the performance of x?", lacking context. Hope that helps, Dan. On 4 January 2013 23:56, Joerg Fritsch <[email protected]> wrote: > Hi, > > what are currently the most appealing use cases for River? What are the best > deminstrators that do show that River is what the world needs :D ? > > --Joerg >
