reactiveservices VS Meteor JS

https://github.com/intelix/reactiveservices

And the screenshot is the early version of the real app built on it

Conceptually it's the same to what described in conductor, however you are in full control how the data is synced, how and to what you subscribe etc.

It was built, first of all, for the application in forex trading, so there are some "specific" features, such as optimised binary stream with delta-only updates, priority on the data streams, demand-based backpressure, subscription based on the visibility of the data, very low latency, cross-dc clusters and many more.

How it works is described (in rather over-simplified way) on the github page. There's a choice of scala or java on the back end, and react on the client side. Websocket only. Like I mentioned, the currently exposed source code is not maintained and based on the very version of react (there are still mixins in the example), and has some vulnerabilities.

The latest version of the framework is maintained in the private repo, and we have built a number of solutions on it over the years, and not only in the forex space. It is well suited for most Single-page apps.

Latest version uses latest react features, hooks based, and the server side has seen significant changes as well.

Why we decided to keep it private? We thought world already have enough web frameworks, and since, we thought, our framework and approach was such a niche, we just kept using it for our clients and our own projects. But since then we have been surprised how easily it could be applied to other fields, and yet there's still nothing like this is available. GraphQL with subscriptions probably is the closes, but not good enough.

Is there any interest in something like this in the community? If so, we can definitely make large parts of the framework, which is now 6yo, public.

As you might have seen from this PR and in our forums Meteor v3(it is still in beta, but you can follow the progress here) will be released with a new engine, expressjs.

We are in the process of migrating documentation from the current site to the new one. You can follow the status in this PR, and the preview site is here. In the near future, we will move our guide to the same site.

We are in Meteor v3.0-alpha.19. To see what is missing for our beta and official release, you can check this GitHub discussion here.

Community stats: The Meteor.js GitHub repository has an active community with 43.8k stars and 5.4k forks.

Finally, the release of Node 16 became basically incompatible with fibers and thus, Meteor.js got stuck on Node 14. This implied a major rewrite of a large potion of the platform's internals as it all depended on fibers. Further, it implied that all Meteor.js projects and packages required a major rewrite as well.

So, I found this project to be at release 0.8.3, which is from June, 2014. The latest available documentation are the release 1.3 docs. The related 1.3 release is tagged on GitHub from 2016, so there is basically a gap of two years in between this.

Making the Meteor.user API clearer

You need to have Meteor installed on your system. Follow the Meteor installation instructions on the Meteor website.

Meteor.js is a full-stack JavaScript platform for developing modern web and mobile applications. Meteor includes a key set of technologies for building connected-client reactive applications, a build tool, and a curated set of packages from the Node.js and general JavaScript community.