Original Summary

We're building a software product where different users and parts of the system need to send messages to each other. It's not really a chat app. Messaging is just one part of a larger business application. The basic requirements are: the application can create users and communication channels users can be added to channels with read/write permissions messages sent to a channel are stored and delivered to the relevant users if a user is online, we'd like to deliver messages in real time if they're offline, the message must still be there when they come back our backend may also need to send system/workflow messages, not just messages written by people ideally, different applications could receive new messages through something like WebSockets or webhooks, with polling as a fallback So basically we need a reliable messaging layer underneath our application, while we build the actual UI and business logic ourselves. We're trying to decide whether it's worth having our developers design, build and maintain all of this, or whether we should use an existing service. Has anyone here had to make a similar decision? Did you build it yourself, or use something like Firebase, Ably, PubNub, Pusher, etc.? And looking back, would you make the same choice again?   submitted by   /u/Capable-Court-3811 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/22 04:14:34