Most frameworks support either REST or WebSockets, and don't make it easy to switch between the two, and/or support both styles of application at the same time. WebSockets offer many advantages over REST, eg:
- most benchmarks show WebSocket messaging to be significantly faster than over HTTP
Something that shot up the popularity stakes last week was this article on a very interesting initiative: RealWorld:
https://medium.com/@ericsimons/introducing-realworld-6016654d36b5
I decided it would be a good idea to use this as a way of creating an exemplar implementation of a RESTful back-end using QEWD against their published API (https://github.com/gothinkster/realworld/tree/master/api)
The results are here:
https://github.com/robtweed/qewd-conduit
Actually it's the first 3rd-party implementation out of the blocks!
I've mentioned the QEWD project in this group before: it's a Node.js-based platform for web, Native and REST applications which tightly integrates with Cache. It uses a somewhat different philosophy to the use of Node.js than the norm, and I've now published an article that explains this approach and the unique benefits that arise as a result.
It turns out that, integrated via QEWD, Cache is an ideal bed-fellow for Node.js. QEWD makes the integration of Cache and Node.js exceptionally fast, simple and intuitive to use, but also extremely powerful.
Read the article here:
Some folks here may find this interesting:
https://groups.google.com/forum/#!topic/enterprise-web-developer-commun…
See
http://www.datasciencecentral.com/profiles/blogs/ten-top-nosql-databases
What will it take before Cache begins to appear on (or at the very least be considered for) such lists?
I've released a comprehensive, free online training course on the new EWD 3 suite of products that allow the integration of Cache with the burgeoning Node.js world, and allow you to create and run browser-based and mobile applications with all the very latest development technologies from the JavaScript world.
Some may think it's a strange / daft idea, but just today the Raspberry Pi folks have announced that they've now sold more than 10 million of them..and counting. That's a huge potential marketplace, and a great platform for getting people to hear about Cache and try it out. Given its focus on the education sector, another great way of getting heard about.
Interesting to see this latest ranking come to my attention:
http://db-engines.com/en/ranking/graph+dbms
Look what's ranked 16th. Shame a decision was made to deprecate it 
Today I'm releasing a new EWD 3 module - ewd-feder8.
ewd-feder8 is a federation or integration platform, built as an extension of the EWD 3 ewd-xpress module. So what does it do and what's it for?
It's all about federating and integrating multiple web or REST service end-points.
At its simplest you can use it as a proxy server in front of a remote web service or REST end-point.
In this article I'll describe how to set up web services and/or REST services using EWD 3.
Since EWD 3 is designed to be modular, you can construct the environment that exactly meets your needs, but for much of the time you'll probably find that the pre-built EWD 3 ewd-xpress super-module does most of what you need because it hooks together all the core EWD 3 and other building-blocks you'll need:
Those of you who keep an eye on developments in the mainstream of IT will be aware that a major upheaval has been occurring over the last 5 or so years, in which JavaScript has exploded in popularity and importance. Largely as a result of its server-side incarnation - Node.js - it has broken free of just being the scripting language that you use in web browser, to becoming the world's most popular language and enterprise technology of choice.