Many developers reach for WebSockets or libraries like Socket.io the moment something needs to feel 'live'. In many cases, this adds unnecessary complexity.
For features like live counters, presence indicators, or collaborative editing previews, I've had great success with a combination of React Server Components, smart revalidation, and optimistic UI updates.
Using Next.js revalidateTag and revalidatePath strategically has allowed me to keep data fresh without the overhead of managing WebSocket servers or scaling concerns.
The key is understanding your actual requirements. Does the user need sub-second updates, or is 5-10 seconds acceptable? Most SaaS use cases fall into the latter category.