Sigh, maybe Client-Server or Remote Data Access?:<p>&quot;3.4.7 Remote Data Access (RDA)<p>The remote data access style [131] is a variant of client-server that spreads the application state across both client and server. A client sends a database query in a standard format, such as SQL, to a remote server. The server allocates a workspace and performs the query, which may result in a very large data set. The client can then make further operations upon the result set (such as table joins) or retrieve the result one piece at a time. The client must know about the data structure of the service to build structure-dependent queries.&quot;<p><a href="http:&#x2F;&#x2F;www.ics.uci.edu&#x2F;~fielding&#x2F;pubs&#x2F;dissertation&#x2F;net_arch_styles.htm#sec_3_4" rel="nofollow">http:&#x2F;&#x2F;www.ics.uci.edu&#x2F;~fielding&#x2F;pubs&#x2F;dissertation&#x2F;net_arch_...</a><p>REST is a very specific architecture, with very specific constraints. Not everything <i>is</i> REST, not everything <i>should</i> be REST. And there&#x27;s certainly no reason to call things REST, if what one means is simply a client-server application over HTTP. But if what one is building is &quot;just&quot; client-server, perhaps <i>HTTP</i> isn&#x27;t the best transport.