radar-base / fcmxmppserverv2 Goto Github PK

Use a different database for storing subject info and messages sent and delivery stats for each subject.

This will also help track the association between FCM tokens and subject IDs

Related to #6

Add last request time metric for each subject which will denote when the app was last opened or last interaction since the notification requests are sent whenever the app is opened.

Persist the delivered schedule for a configurable length of time for schedule provenance.

This will need modification of the cancel functionality to not remove any delivered notifications.

https://sentry.io/welcome/ is a very nice tool that takes this info from the logs and provides valuable insights.
Also they provide it for free for open source projects

Right now each request is scheduled as it is received but we can have some sort of time based caching that accumulates the requests and processes them all together (after some time or based on the number of entries) since the requests will probably come in bursts.
A nice one to use is CacheBuilder from Guava library

Use the delivery_receipt_requested parameter in the FCM payload to get a delivery receipt if the notification is delivered.

Right now, the tasks are scheduled even if the task with same token and subject id with exactly the same time already exists.
An alternative way to schedule should be included which is based on time and equality of notification.
If notifications are exactly the same and scheduled time is also the same, these should be ignored.

Investigate the feasibility of moving from Spring JDBC to Spring JPA for better interface with the database and not handling raw queries.

We can send the delivery information of a notification to a kafka topic using Rest Proxy.
This will help in calculating the compliance of subjects.

Depends on #7 and #6

Create a Simple web app with UI for accessing notification details for each subject.
Probably should take project and subject info from MP after authenticating with the MP using authorization code or password grant type
At first this can just be basic auth with info of all participants available to everyone.