Is Using Websockets for a Backend-Driven App a Good Idea?

We do a mixed approach: we use websockets for live updates (like scores) and REST for stateless operations (like authentication and config). Going websocket-only can complicate debugging and load balancing. If your server handles all calculations, it might work, but I’d keep authentication and configuration on REST for simplicity.

If you're mainly sending data one way, you might want to use Server-Sent Events (SSE). Websockets are best when you need real-time, bidirectional communication, but for what you've described, SSE could do the trick.

Yeah, using websockets definitely works for your app, especially since it needs to show real-time updates for long-running tasks. Just keep in mind what constitutes an "update"; it might draw you into complexities similar to frameworks. Stick with basic state updates in simple JSON so the frontend can easily display the results.

Your websocket-only design is valid, particularly for real-time updates during calculations. Just remember, it means the backend is the main source of truth for your app’s state, which can lead to more complexity. Also, consider if any calculation logic should be pushed to the client to reduce backend load.

You're on the right track with websockets, but have you thought about server-sent events? They might be an easier alternative for your setup. They’re great for just pushing updates from the server to the client without the complexity of full websockets.