speedtest
SocketCluster
speedtest | SocketCluster | |
---|---|---|
5 | 9 | |
208 | 6,115 | |
- | 0.1% | |
0.0 | 6.8 | |
about 1 year ago | about 1 month ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
speedtest
-
Big PleX server problem, constant buffering when attempting to watch almost anything
I use this one, and works very well. Very lightweight just needs to be on a webserver or (i think) they have a docker image.
-
Press 'Enter' to Run a SpeedTest (Update v2.5.4) - Self-Hosted SpeedTest - Docker
I really like this project in compare to LibreSpeed or Speed Test, since it doesn't requires docker, PHP, nodejs or other heavy stuff, just a static web server is sufficient for a quick local speed test!
- Internet magically gets faster when opening speedtest?
-
Directory Traversal Bypass on e7d Speedtest
The application is hosted here: GitHub - e7d/speedtest: A self-hosted, lightweight HTML5 speed test implemented in JavaScript, based on Web Workers and XMLHttpRequest.
SocketCluster
-
The Sound of Software
Recently, I added an AI-generated soundtrack to my open source project's home page https://socketcluster.io/
It seems unconventional at first but I distinctly remember about a decade ago when Adobe Flash was still broadly supported, many Flash websites had soundtracks. I think the reason why regular HTML websites didn't have them was because it was difficult to implement and internet was much slower so they had to be streamed in a special way.
-
Is it a good practice to store web sockets connections on redis?
If redis doesn't satisfy your requirements or you're unable to make it work using adaptor, SocketCluster is a great package for this https://socketcluster.io/
-
Why messaging is much better than REST for inter-microservice communications
Interesting how this feature set is pretty much exactly the same as offered by SocketCluster https://socketcluster.io/
-
On the Unhappiness of Software Developers
This resonates with me 100%. Every bit of unhappiness I've felt in my career so far has been caused by a bad manager. The main issue for me has been the final point you mentioned about "Imposed artificial limitations" - I cannot tell you the number of times that I've been forced to use an inefficient tool or do something in a sub-optimal or downright incorrect way (knowing that it would have to be re-written later) by a bad manager... In some companies, it was a daily occurrence; that's why I never stayed at a single company for longer than 2 years. It's almost impossible to find a company that lets me implement things correctly.
Thankfully, nobody could constrain me in my open source work. I (with the help of community members) built:
- SocketCluster (https://socketcluster.io/): A distributed pub/sub framework.
- Capitalisk (https://capitalisk.com/): A lightweight quantum-resistant blockchain which is less than 5K lines of code.
- LDEX (https://ldex.trading/): A deterministic decentralized exchange (DEX) which can work with many different blockchain protocols. It's less than 4K lines of code in total and only has 3 small third-party dependencies (including sub-dependencies).
-
Looking for real-time message solution recommendations
The two best lightweight solutions I have worked with are SocketCluster and NATS. SocketCluster is used to build out a custom backend that scales very well. NATS would be used as a central pub/sub system. If you need queueing, you'll need to add additional services like Redis.
-
How to define RPC server with SocketCluster.
In the homepage for SocketCluster it is mentioned that it is a Highly scalable pub/sub and RPC framework optimized for async/await. However in the documentation I have not found anything related to RPC. Am I interpreting anything wrong here?
-
Top WebSocket libraries for Node.js in 2022
At the time of writing, SocketCluster has almost 6k stars on GitHub and 7k downloads on npm weekly,
-
SocketCluster. The most underrated framework. Part 1: Intoduction
SocketCluster is a framework which allows you to use the WebSocket protocol the transmit between its backend API and client library. The client can be used both on a backend (E.g. a Raspberry pi) or frontend application.
What are some alternatives?
mtr - Official repository for mtr, a network diagnostic tool
Socket.io - Realtime application framework (Node.JS server)
speedtest - Self-hosted Speedtest for HTML5 and more. Easy setup, examples, configurable, mobile friendly. Supports PHP, Node, Multiple servers, and more [Moved to: https://github.com/librespeed/speedtest]
deepstream.io - deepstream.io server
docker-speedtest-analyser - Automated docker speedtest analyser tool with included web interface to monitor your internet speed connection over time. Setup at home on your NAS (Synology, QNAP tested) and the container runs hourly speedtests. The speedtest results are displayed in an webinterface as line graph(s) over the day.
Primus - :zap: Primus, the creator god of the transformers & an abstraction layer for real-time to prevent module lock-in.
prometheus-connectivity-exporter - A network connectivity prober for Prometheus.
SockJS - WebSocket emulation - Node.js server
speedtest-to-influxdb - Script to periodically run the Speedtest CLI application by Ookla and post results to InfluxDB.
Faye - Simple pub/sub messaging for the web
internet-speed-monitor - Internet Speed Monitor With Prometheus Metrics
Straw - Realtime processing framework for Node.js