Socket.io VS deepstream.io

The example works just fine in my code, the problem is the adding of the player is automatic, i receive a socket.io saying add the player, then it calls a function to add the player. I'm struggling to understand what to bing the .once() call to make this work. I dont want it to be interactive with the user, just to happen in the code... Anyways, thank you i'll keep poking around to figure out how others have achieved this.

With a backend, you should prefer websockets for normal in-game communication and REST API for other communication like authorizing the players, etc. socket.io is a really popular library for implementing websockets.

My socket.io -client was not the same version as the socket.io server side.

Got it. And socket.io? What is the difference between them?

const io = require('socket.io')(server)

My current skill level is successfully using javascript and frameworks such as express and socket.io to build a multiplayer retro 2D tank game (something like BattleCity in the 1980s). This is the only project that I have done.

Server platform Node.js, going with the real-time data exchange library Socket.io helps build a chat with unlimited customization possibilities.

It really doesn't matter if you are standing up a websockets server (examples being socket.io or signalR). Matters even less if you use a platform like Twilio Conversations API or GetStream.io.

I have a socket.io nodejs server. Was wondering how do I scale my application for large number of concurrent users (say 10k) in AWS.

Yes, the application has many concurrent users daily and we are building a new feature/ service which uses socket.io for real-time communication.

I'm working on a few projects, from one/two days to platforms.

The first is OS and is a simple nodeJS environment to deploy applications via lambda and express quickly. Sort of like nestJS except less decorators and more functional (https://vramework.io/). I already know of a few other colleagues that rolled their own propriety versions of this to support enterprise and cloud deployments so decided to OS it.

The other OS project is a strongly typed postgres/mysql driver. The idea is to generate typescript definitions directly from postgres (https://github.com/vramework/schemats) and then have a think layer ontop of pg-node that gives you strongly typed queries (https://github.com/vramework/postgres-typed).

An open-source project I spent a few years on the core team is https://deepstream.io/, a realtime-server that allows you to mix and match multiple streaming protocols (mqtt/websocket/others) and allow those clients to talk to each other using pub-sub and records. I'm not longer working for it but wanted to give it a shout out!

On a non OS project, I have been working on an immersive audio platform for a while now. The main goal is to allow users to pick and choose how audio books progress, and also have a live session mode which allows users to record their pulse / answer questions and a few other metrics and associate it with sentences. I pretty much built and deployed all of it but require some advice/brainstorming on how to proceed now. I built it to satisfy an itch when I was practicing shamanism during the first lockdown when I was in-between contracts / taking time off.

I also want to build a simple web-pages strategy game based around eco-education, but don't have the bandwidth . If anyone is interested in mixing together gamification and eco-village building might be a fun conversion to bounce ideas!

All the OS projects above were used to support my personal/a couple professional projects over the last few years.

Email in profile

I'm currently looking for a contract that is part-time that is focused on consultancy or smaller projects (such as setting up containerized AWS environments)

I am looking for part-time contract or freelance/consulting opportunities at the moment (up to 20 hours/week).

GitHub: https://github.com/yasserf

OS projects I am/was core maintainer of: https://vramework.io/ and https://deepstream.io/

LinkedIn: https://uk.linkedin.com/in/yasserfadl

Email: [email protected]

https://deepstream.io is the closest and has a richer feature set (including a replicating document store), however it seems to have a small ecosystem / community / limited support options, and permissions do not seem as advanced.

https://nats.io is close but lower level. Has a large community and rich ecosystem however.

Then you can also mix and match lowever level technologies to achieve the particular set of tradeoffs you need. MQTT, AMQP as the protocol, mosquitto / rabbitmq/zeromq, then json-rpc on top ...

I can find socket.io, faye, deepstream.io , autobahn-js and nchan, centrifugo. Can you also explain why you chose it and if you had troubles with some other solution?