RE: [Jersey] JAX-RS == REST? Or not? (was Re: [Jersey] What HATEOAS actually means)

From: Markus Karg <>
Date: Thu, 18 Feb 2010 20:48:11 +0100

> However, it must be understood that the architectural properties are
> not those of REST-style systems. And it must also be understood what
> the architectural properties of those systems are. REST trades off
> certain properties (e.g. performance) to gain certain other properties
> (e.g. scalability).

Actually I won't share this in general: REST is not mandatory slower than
other architectures. For example, when we turned from RPC to REST we noticed
actually that the per-transaction-time was improved. The reason was that
loading the client's state from the database at each single step in the
workflow actually needed longer that processing the XML provided by the
client with every RESTful workflow step. Why? Because the client kept it in
RAM, while the server went out of RAM due to all the lot of clients and
started to swap. So, the improved scalability here went along with
*improved* performance actually!