It was brought up to me that it may be best to avoid using SQL as a central repository of data all together, and that we could potentially just use a simple P2P style set up instead. At first I was having a hard time conceptualizing this but here are some notes for how I think it would be doable:
- The only data that would be required to send around to all users would be the current stack info, which is simple to track and can just be speaker positions, name, and a UUID for identification.
- Ensures that all notes kept by mods are kept client side rather than in a central repository, reducing data leakage potential.
- We can keep the rest of the majority of the Go server side app. Really all we would need to do is rip out the SQL portion of it and move that kind of tracking functionality into the client side app, which honestly is a pretty simple move. This would also allow me to simplify a lot of the Go code to literally just websocket management.
It was brought up to me that it may be best to avoid using SQL as a central repository of data all together, and that we could potentially just use a simple P2P style set up instead. At first I was having a hard time conceptualizing this but here are some notes for how I think it would be doable: