novu trigger and scaling question
Hello, My system has subscribe model, user can subscribe to post and comments.
When user creates post (and user is subscribed) i have to send thousands of notifications, when someone comments, send to all except owner of comment.
Another case is, im holding device group on my own for now.
My frontend is flutter. Shame that i cant use your components 🙂
Questions:
1) multiple subscriberIds in novu trigger or sent novu trigger per user?
2) is scaling supported on selfhost? How about sockets?
3) is there a way if user has multiple devices, when notification is clicked on one device, its removed from other devices?
21 Replies
Hi @the_nexen
1. You have to send trigger per user
2. @dimagrossman can help here
3. If it is for in-app notification using our notification center, yes it will be in sync with multiple devices for same user (subsciberId)
Thank you! ill then try to set it up and do some tests. If this would cover social apps, then it would be amazing!
@the_nexen regarding your usecase, we are working right now on a Topics functionality, where you can create custom topics and subscriber users to it. Once you have an event you can actually send a notification for the topic key and we will fan it out for you
awesome! is there a limit how many topics can user have?
Do you have an estimation of subscribers?
For a particular topic
when we talk topics, topic for particular post, topic for particular post-comments, topic for group chat, topic for particular direct chat, topic for products, topic for orders
it gets easily out of hand. For past month im trying to make a system that is lightweight and smart. From my point of understanding: new post - new topic.. based on FCM, if there is 2001 posts, im done. Hope you know what i mean.
Estimates for 2Q is 10k users, but overall for a year is 2-3m users
So you will create a topic for each post you have in the system so a topic key would like:
post-1234 where 1234 is the post id in your system. We won't have limit on the. number of those you can create
After that, individual subscriber can subscriber a particular topic-1234 for example and get notifications for itgotcha, thank you! And whats the estimate of topics arrival ?
@the_nexen, you just advanced to level 1!
Should be available next week 🙂
oh, that soon? amazing!
Yes, we already finished with it, now finalizing the 0.10.0 release 🙂
thats amazing, glad to see progress so fast 🙏
Btw i was looking again for the scaling and i didnt get an answer @dimagrossman, could you please tell me? We already use hasura with postgres and planing kubernetes
Hi @the_nexen sorry, missed the mention.
Scaling when self hosting is really up to you, don't have any specific concerns as the system is built around allowing creating multiple instnaces of the API service.
Internarlly we auto scale based on load, I don't have any specific kubernetes guides or similiar since we are working with a managed ECS service for that.
Just a mention, you will have to use mongodb for novu and not your postgres configuration
@dimagrossman understood. If postgres was available in novu, it would simplify a looot of things for us, but either way, novu is the best thing i stumbled upon
@the_nexen, you just advanced to level 2!
Yeah I know, sorry about that. Just it would be very hard to support all databases. Some use mong, some postgres, some elastic and etc... For now it would be not practical to add supprot for SQL db's and also maintain it in the long run
@the_nexen In the new version (coming soon - current me if I wrong @dimagrossman )
You would be able to tag multiple users and then trigger the notification for the tag
i completely understand. Hopefully in the future, this could be done. For now mongo is fine for us
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
How do you plant to store the data in BJSON columns and keep the same schema structure or to do it in the classic relational way with dedicated columns for every field of the entities?
Asking as the first one could be less of a hassle to implement doing a bit of face lifting in the DAL library. The second one would need a lot of maintenance work to keep up with the Core development in future versions.
I can share the pain of being limited in the DB choice but unfortunately we do not have the resources to offer that flexibility for now. 😦