kba commented on Aug 21, 2015
A nice extension of the current functionality is to allow "transient" or "ephemeral" writes -- meaning writes of data to be disseminated to all current listeners but not persisted in the database. This would be useful for data that quickly loses its value with the passage of time, e.g. statistics about current connections. This amounts to skipping the DB operation and simply posting the data to the message queue -- conceptually very simple. The data would have to be marked as transient so that clients would know not to persist it in local DBs as well.
This seems like a potentially useful enhancement but we need to validate that there are real user requirements for it before applying resources.
kba commented on Aug 21, 2015 A nice extension of the current functionality is to allow "transient" or "ephemeral" writes -- meaning writes of data to be disseminated to all current listeners but not persisted in the database. This would be useful for data that quickly loses its value with the passage of time, e.g. statistics about current connections. This amounts to skipping the DB operation and simply posting the data to the message queue -- conceptually very simple. The data would have to be marked as transient so that clients would know not to persist it in local DBs as well.
This seems like a potentially useful enhancement but we need to validate that there are real user requirements for it before applying resources.