colyseus VS plane

If you don't want to dive deep into backend then https://colyseus.io/ might also be an option.

Since you already know Javascript you could try to use some existing server framework at first to avoid having to do everything from scratch. https://github.com/colyseus/colyseus

Try this Node.js based server framework https://github.com/colyseus/colyseus

https://colyseus.io/ (Authoritative server, that works with many engines JavaScript/Phaser/Unity/Haxe/Defold)

If you want web based you'll likely use Javascript for frontend/client. Check if this JS game server framework has what you need https://github.com/colyseus/colyseus

Also check Colyseus. Bit similar multiplayer server framework and built on top of Node.js/TypeScript. https://github.com/colyseus/colyseus

The above project uses a Node.js authoritative game state called Colyseus (https://github.com/colyseus/colyseus) which handles the state synchronisation between clients and server.

We use Colyseus for this. Pretty easy and open source too. https://colyseus.io/

One reason I'm excited about this is that it appears to let you write arbitrary routing logic into a layer 7 proxy. This is something we had to build for https://plane.dev and it would have been nicer to use something like this, but we couldn't find anything like it at the time.

Of course, as a user, I would prefer as much as possible to be under MIT or Apache. See for instance https://plane.dev/ for a similar project which is MIT licensed and https://jamsocket.com/ for the commercial version.

From an earlier blog post[1], the system for synchronizing file/document state lives independently for their database. As I understand it, their database is for metadata rather than actual document content.

> It’s worth noting that we only use multiplayer for syncing changes to Figma documents. We also sync changes to a lot of other data (comments, users, teams, projects, etc.) but that is stored in Postgres, not our multiplayer system, and is synced with clients using a completely separate system that won’t be discussed in this article. Although these two systems are similar, they have separate implementations because of different tradeoffs around certain properties such as performance, offline availability, and security.

This post[2] goes into more detail on how they spin up backend processes to serve as the source of truth while documents are open (we took heavy inspiration from it when building https://plane.dev, which aims to be an open-source implementation of that architecture.)

[1] https://www.figma.com/blog/how-figmas-multiplayer-technology...

We have been happily using Depot for months now to build https://plane.dev. Prior to finding Depot, we basically gave up on building an M1 image from a GitHub action.

(btw, I always get suspicious when a Show HN post has a lot of praise in the comments, but I swear the Depot folks did not ask me to post anything and I only saw the post because I was checking HN)

Congrats on the launch!

We've been using Depot with Plane (https://plane.dev/). Prior to depot, I had to disable arm64 builds because they slowed the build down so much (30m+) on GitHub's machines. With Depot, we get arm64 and amd64 images in ~2m.