java - TIme-based Notification Architecture -


i designing notification service (server). can have 2 kinds of notifications: 1 delivered immediately, , other delivered @ time in future.

is there framework handle future notifications?

i know can write background worker can example sample db notification needs sent, sure millions tried solve problem , i'd prefer reuse proven solution.

i didn't decide yet on framework / db. thinking should use either vertx.io or jetty (websockets) push notification. not sure regarding db because wanted support future notifications.

update: how recommend should save data in db "live" notifications (notifications exists in users inbox) , future notifications?

update: thinking of using either:

  1. jetty + spring websocket & sockjs + quartz
  2. vertx.io (supports websocket , sockjs)

any recommendation?

one approach deliver notifications scheduling component. scheduling component consumes notifications, stores , checks regularly see if notification due sent out.

this allow attach listener notifications , not pile notifications @ publisher side.


Comments

Popular posts from this blog

sublimetext3 - what keyboard shortcut is to comment/uncomment for this script tag in sublime -

java - No use of nillable="0" in SOAP Webservice -

ubuntu - Laravel 5.2 quickstart guide gives Not Found Error -