Hey everyone! I'm diving into websockets for my project where I'm implementing features like profile modifications and private messaging on my website. I've read that while websockets are awesome for real-time data updates, refreshing the page to load the latest data may be frowned upon. For instance, think about Twitter—how annoying would it be if you had to refresh to see new tweet replies? I'm using Django for the backend and React for the frontend, so I want to make sure I'm using the best approach. I recently discovered that if I call the API to fetch user info upon a successful save, it works really well and is pretty straightforward. However, I'm curious to know if this method scales well with a site that might see 100,000 users daily.
7 Answers
If you just need to know about new posts, it's fine to check for updates without refreshing everything. For an activity feed, periodic checks can be great. But web technologies are evolving, and you might find that simpler solutions like SSE or even long polling could work for you depending on your needs.
Using websockets can significantly reduce data use, especially beneficial for users on mobile connections. Plus, they lighten the load on your server during peak traffic since users can receive updates without needing to refresh. However, if your site doesn’t necessitate constant updates for a smooth user experience, the complexity of setting up websockets might not be worth it.
Honestly, refreshing the page isn't ideal. If you're working with React, you can easily fetch data using JavaScript without a full reload. Set an interval to request updates and use React's state handling to dynamically render the data on the page. This is pretty much the core of what makes React so great!
You might consider having a refresh button, but it's not the most user-friendly solution. Most sites are designed to avoid page reloads for data updates. If you're looking to build something like Twitter, make it smooth and seamless for users.
You could definitely just fetch and update only the parts of the page that need it without doing a full refresh. We've gotten so used to seamless updates, but that doesn’t mean every site needs to implement websockets. There are simpler methods like short polling or server-sent events that could work just as well.
Polling for new data every few seconds can be a bit much for your server, especially if you have thousands of users on your site. Instead, consider an intelligent polling mechanism that checks user engagement. This way, if users aren’t actively using the page, you won’t overload your server with requests. Caching the poll results on the server could also help minimize database hits.
That makes sense! In my project, I'm currently refreshing the page after a user updates their profile. But it's a hassle because I can’t show success messages without more complicated code, and it’s not very user-friendly.