In my previous apps , I dealt with User - Notification tracking by keeping a Notification Table consisting notificatoons of all users and tracking it per user by having a Sender´ andReviever´ Column per user.
But I think that this architechture would turn out to be inefficient ,slow and irrelevant when the user base is high. So , What could be the alternatives of this architecture . ( Push notifications are there for without Polling data fetch but I want them to be network reterievable and store in the databases).
I thought of something like an Inbox´ Architecture where there shall be column namedNotifications´ and every new Json for A notification object might be appended on and on for the user. But I don’t know still if this is good.
I would like to learn from the other developers as well as Backendless moderators on how they`d implement this scenario effectively.
Thanks. 
Hi Pujan,
I hope other users will chime in and share their opinions. As for the support staff, we focus exclusively on problems and questions related to Backendless API and backend functionality.
Regards,
Mark