Downloads provided by UsageCounts
We present results of using the in-memory database Redis in processing transient event alerts. The Redis works in two different ways for processing alerts. First, the publication-subscription model in the Redis allows us to adopt it as a message delivery system for multiple local alert clients. Second, we use the features of indexing and storing geolocation information in the Redis to enable low-latency matching of transient locations with custom catalogs. The current system collects event alerts by using VOEvent streams and detecting changes in web pages/feeds. We also introduce our efforts of migrating the system from the Redis message delivery environment to the NATS-based message processing configuration as well as application of Uber's H3 spatial indexing model instead of the Redis geolocation support.
transient, Redis, Tile38, NoSQL, NATS
transient, Redis, Tile38, NoSQL, NATS
| citations This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
| views | 15 | |
| downloads | 15 |

Views provided by UsageCounts
Downloads provided by UsageCounts