Highly scalable pub/sub and RPC server/client pair
Australia
Joined May 2014
- Tweets123
- Following111
- Followers471
- Likes84
SocketCluster retweeted
Saasufy.com no-code platform now supports granular, field-level access control and blockchain-based authentication for your app.
Token symbol: SAS ldex.trading/trade/#market=s…
Today marks over 10 years since SocketCluster's first GitHub commit. Still going strong. #javascript #nodejs
SocketCluster retweeted
Good OOP code is about messaging. If you want to catch a taxi, you just need to tell the driver the address (argument is a string). You don't need to pass him your own car seat and petrol. #programming #Coding #OOP
We recommend using socketcluster-client integration tests as documentation: github.com/SocketCluster/soc…
SC client and server have over 5000 of lines of test coverage... Probably more lines of test code than actual project code. #Node #javascript
We've made an update to SocketCluster client and server to fix a bug in an undocumented but potentially very useful feature.
You can call '.once(timeout)' on any event stream to make it throw an error on timeout:
#javascript #Node
SocketCluster's focus on fault-tolerance is key to allowing you to write pub/sub logic using declarative syntax. There is no need to handle every possible error with try-catch, or to imperatively reconnect and re-subscribe to channels on network failure. socketcluster.io/
Writing a reliable pub/sub system from scratch is challenging because handling all possible permutations of error and recovery scenarios is extremely difficult. Especially when you factor in different authentication states and per-channel access control.
SC has been tested to handle all these scenarios in an efficient and fault-tolerant way. See github.com/SocketCluster/soc… and github.com/SocketCluster/soc…
Looks like the latest #ChatGPT knows how to use the latest SocketCluster version... It also knows about more advanced patterns like filtering a stream by wrapping it in an async generator. Impressive!
With the standard emitter/listener approach, each event is processed in parallel; you have no control over the processing order.
With SC's async generators approach, each event is processed sequentially by default but can be processed in parallel if required.
Such race conditions are both common and also difficult to identify and reproduce; this makes them a major security threat.
Race conditions are the worst kinds of bugs. SocketCluster socketcluster.io/ is designed to help you avoid them. By default, every RPC call in SC executes and returns in-order, even when there are async operations involved. There is no other toolkit like it.
SocketCluster retweeted
LDEX (lisk-dex) ldex.trading/ LSH/LSK market has been running for over a year with a 1K LSK ($4K USD) bug bounty. No hacks or critical bugs reported. Its strength is in its simplicity; the lisk-dex module is only around 4K lines of code in total including dependencies.
SocketCluster retweeted
Remember this Tweet thread I posted last week? Read it again, then check out this news (out yesterday): barrons.com/articles/alphabe…
They accidentally revealed a new economic phenomenon and decided to cover it up artificially.
I wrote about it last month: jonathangrosdubois.medium.co…
SocketCluster retweeted
Does any blockchain aside from Capitalisk capitalisk.com/ allow an account/wallet to change their passphrase?
14%Yes, I know of others
71%No, never heard of this
14%Not possible! You lie.
7 votes • Final results