Good morning to all forum guests,

we developed a Java client-server applications, in which remote application server and java client (traditional java swing clients) communicate via http connections, using Data Transfer Hashmap pattern: classes (simple JavaBeans or POJOs classes) are serialized in a compressed stream and sent to the remote application server, which replies with same approach.

Now, we're evaluating how this solution impacts on network bandwith usage. We discovered that, while in mean each request/response  requires a payload of about 20-40 Kbytes, in some cases (mainly, when requests or responses are involving trasmission of lists of objects, even of 3/4 hundred of items), the payload reaches 200 / 300 kbytes per request / response.

I wonder if this communication architecture were a bad choice, so that we would try another approach
before experiencing bandwith shortage, or if this payload should be considered "normal". For example, a rich web application (with a non-spartian or minimal user interface) how much network band consumes in mean ?

Do you have any suggestion or hint ?

Thank you in advance !