Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Remote Query

RemoteQuery (RQ)

An efficient middleware for friends of SQL, Java, Python and more ...

  • With RemoteQuery (RQ) you get a simple but powerful tool for creating backend services for web, mobile or standalone applications.

  • With RQ you can use existing databases and database objects without changes.

  • With RQ you can solve access requirements in a powerful and simple way.

Currently, we have a Java, JavaScript (Node) and Python implementation ready.

Just another object relational tool like Hibernate or JPA ?

Yes indeed, but a much lighter and more efficient one. RQ does not introduce another level of complexity and uncertainty. RQ does not provide a sophisticated and magic mapping and optimization for DB access. All data access is done with explicit SQL statement like select, insert, update, delete or stored procedures.

We strongly believe that the database and the SQL query developers togethr can build the best queries.

Further, after years of the object to relational mapping, it seems obvious that a good relational database design is very important and should not be restrained by an additional layer such as Hibernate and JPAs.

After starting with RQ the Java source code was reduced - even using JPA and Hibernate - by 80 per cent. On the other side, the RQ code, of which 90 per cent are just SQL statements, has been proven to be easily maintainable and testable.

The Highlights:

  • The most simple RQ service is an SQL statement
  • Any RQ service can be protected with a list of roles
  • SQL parameters are directly mapped into the query (still preventing SQL injection)
  • A Java class (or Python function) can be used for a RQ service
  • RemoteQuery are Microservices!
  • A simple yet powerfull object-relational support without obfuscation is provided for the Java and Python coding OR Support

RemoteQuery Services are Microservices!

According to the Microservices? Please, Don't (DZone) and Microservices (Wikipedia) the following criteriae can be applied

Criteria Description
Cleaner Code A simple SQL query is a very clean code statement (if done reasonable)
Easy to write, one purpose A simple SQL query is a very clean code statement (if done reasonable)
Faster than monolith, independently deployable RQ applies no big interception layer such as Hibernate or JPS
Not all engineer work on the same codebase One RQ service is finally one DB entry.
Autoscaling RQ does not assume or restrict anything about scaling.
Small in Sizes (WP) An RQ service can be as small as a single, parameterized select statement.
Continous Delivery An RQ service can be deployed event without re-start of a single component.

Some Microservices criticism and concerns do not apply to RQ!

Microservices criticism and concerns are well described in Microservices criticism and concerns (Wikipedia). Let's look at some and how they are treadted by RQ.

Criticism and Concerns of Microservices Does it apply to RQ?
Inter-service calls over a network have a higher cost in terms of network... RQ does not require any networing other than DB access protocols.
Testing and deployment are more complicated. Due to the simple model of RQ programming testing is very straight forward and independent.
Two-phased commits are regarded as an anti-pattern in microservices-based architectures as this results in a tighter coupling of all the participants within the transaction. RQ bundles a single service (event call sub-services) as a single transaction.
The very concept of microservice is misleading, since there are only services. There is no sound definition of when a service starts or stops being a microservice. We totaly agree on that. RQ does not differentiate on that in any way.

Example RemoteQuery with Web Access

Let us assume we have the following RQ service entry:

-- ROLES        : APP_USER

  FIRST_NAME like :nameFilter 
  LAST_NAME like :nameFilter

The the following URL:


will return - for users with the APP_USER role - the following JSON:

  "header" : ["firstName", "lastName", "city"],
  "table" : [
        ["John", "Maier",  "Zuerich"],
        ["Mary", "Johannes", "Zuerich"]

Example Standalone RemoteQuery

public class Address {
  public String firstName;
  public String lastName;
  public String city;

Result result = 
    new Request()
       .setServiceId("").put("nameFilter", "Jo%")

// convert to a POJO
List<Address> list = result.asList(Address.class);

Quick Start with Gradle

The jar is hosted on by the following dependency definition.

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.12'
    implementation 'com.github.tonibuenter:remotequery:master-SNAPSHOT'

repositories {
    maven { url '' }

(complete getstarted project : Remotequery Java Getstarted

Quick Start with Java

Download or clone this repository. The repository is a Eclipse project (Java Project). It expects Java 8 an later, but RemoteQuery runs with Java 7 as well.

Here some hints for the directory layout of this repository:

  • RQ main : src/main/java/ with java-libs/ is needed for RQ
  • JUnit tests : src/test/java/ with java-test-libs/ together with RQ main
  • Web : src/web/java/, src/web/webapp/ with java-web-libs/ together with Unit tests
  • Documentation : docs/

Python version

See: []


Run the JUnit classes in src/test/java to see how the RQ runs standalone. creates an apache-derby database in the temp directory (see: Files.createTempDirectory) with test tables and services. DB object and services are defined in the corresponding *.sql and *.rq.sql files.

Java Web Container

For running RQ as part of a Java web container just start the remote-query-start-web launch configuration (main class : Open the browser on http://localhost:8080.

Explanation: An embedded Jetty server is started. The web integration of RQ is done by the servlet. The servlet is rather simple. It works fine as a starting point for a web project that applies is own user authentication and authorization.

More details: RemoteQuery Test Setup

Remote Query Documentation