Question: Feasible to use API Gateway Web Sockets + Lambda Instead of EC2? about userbase HOT 2 CLOSED

Thank you @j-berman for pointing out the stateful challenge and providing the detailed information. I'll review the area of code pointed to.

from userbase.

Thank you for your interest!

This would be challenging to implement because our design relies on the Userbase server to be stateful.

When a user signs in, their client establishes an authenticated WebSocket connection to the server. Every user-initiated write operation (or "transaction") is sent over this WebSocket. Once the transaction is successfully stored persistently in Dynamo DB, the Userbase server then pushes the transaction out to all connected clients that have that particular database open.

With this design in mind, the Userbase server is stateful for 2 main reasons:

1. To keep track of which clients are supposed to receive new transactions in real-time.
2. To ensure the server pushes transactions out to clients in the correct order.

This would be a good place to start to see how the server uses state stored in memory to achieve both goals above.

I'm not familiar with the API Gateway, but my initial reaction is that safely replicating the server's statefulness would be the most challenging thing to achieve. I would guess you would need to push that state out to a database, and I'm not sure if the cost/benefit of doing so is worth it (keeping in mind the performance hit from latency + writing to/reading from disk).

from userbase.