Hi everybody and welcome back!
A small recap
Like an actual auction, if you bid for a product, you get counterbids from other bidders. ...
For further actions, you may consider blocking this person and/or reporting abuse
Just wanted to show some love for original articles like this one. ๐งก I'm not particulary React fan, but seeing quality post like yours - you gotta support.
I do feel that WS would be maybe more simplistic approach for notifications, than Socket.io, but I guess that's a preference.
Hi richardevcom, Thank you!
Socket.io basically wraps WS, can you elaborate? :)
While using WS is arguably simpler than Socket.io - I personally find it easier to use for simple notifications. Additionally - performance is noticeably better on heavier usage scenarios.
Yup, The more layers you remove the faster you app becomes.
It's a trade off usually between control and speed.
Same like express and nest.js :)
Did you feel this article helped you? how?
Yes, I was waiting for 2nd part
Happy to give it to you! :)
What should I write about next?
Thanks for this article! Really appreciate your efforts of putting them together.
Thank you very much! Let me know what you are intreseted in and I can write about it :)
I have a JsonDB library lol
npmjs.com/package/@pxe/database
Docs: pxe.vercel.app/docs/database
Do you have a Github link?
I have. github.com/pxe-js
Share your github library here!
How would you handle the load when more users connect. Socket.io fails when it has many connections and requests
Can you elaborate? We can always scale, open more servers.
Also Socket.io offer a sleep mode option to reduce the usage on the server :)
What would you suggest?
Great start! ๐
Which other application use-cases do you want to try with websockets?
Will you try to build a websocket server using Express (without socket.io)?
Let me know if you do! ๐
I am thinking about a chat :)
How are you today? ๐
Thanks for this article man! Learned lots of things about socketIO.
Shared too!
Awesome pratik12350!
What did you learn? :)