After looking at the current REST environment for Drupal 8 it was apparent if better efficiency was needed, then some custom development would be required. I mentioned in a previous post about the work going on in Intermedia which spawned the development of the Advanced Tour and Intermedia modules. One of the projects I'm currently working on which involves the Raspberry Pi running Drupal 8 will evolve to running on a 2.2 Ghz Snapdragon ARM made immediate adjustments to the REST environment necessary. The rest_ui which Klausi released, makes shortcomings in the current REST environment immediately apparent.
For example the current REST resource for entities uses the term 'entity' in the route and also lists {id} for a REST resource using the POST verb. It also listed the original Tour. WTF?
The Tour uses YAML files and not the database content style of other REST entity resources. We eliminated these items by decoupling current dependencies and allowing our REST resources to interface with these other modules as required. This also allowed us to gain other benefits as well without interfering with any of the work already setup to work in the core. All of our REST resources show correctly in the display of the rest_ui. So the REST resources used for the Intermedia, Advanced Tour and Parker GPS modules don't have any of the issues currently conflicting REST compliance with the REST Entity resource.
This is also something we facilitated for the Advanced Tour which was to keep seperate from the original design of the Tour Module which currently has no ability to deal with Intermedia.