Question

We have what I think is a fairly typical client/server architecture, with a frontend written in .NET, displaying data sent from a backend written in Java.

Currently, we use a custom message-based framework for transmitting data snapshots and updates down to clients. This might be upgraded; although the basic java service/.net client setup is set in stone, we want to look at replacements for the message framework, for example WPF MVVM (with an eye on Sliverlight), with databindings to java web-services, or perhaps Coherence.

I was wondering what experiences others have had with this and other approaches (obviously there’s no golden bullet for all situations…).

Our requirements are that the clients can show large, frequently updating and editable datasets, primarily in grids.

Update
I’ve accepted that REST/SOAP is the standard way to do it, but I’d still be interested to hear any other approaches, especially from a performance point of view.

Answer 1

Web services is the most common choice:

• RESTful service – more flexible, no strictly defined schema
• SOAP service – rigid schema, less flexible