Open ryanvs opened 4 years ago
I like the premise of extending some kind of API to allow more real-time notifications. Does it make sense to extend the web API or should this be separate standalone EXE's that can be run as a service and configured appropriately? Kinda like what I've done with Splunk examples? Happy to engage in discussion to see what makes sense.
As we are looking at different technologies I think something that plays well with cloud-based messaging and event notification systems would be of relatively high value. In that respect, AMQP as a first pass seems like it would be a good fit?
I was debating exactly how to structure the solution and projects to accommodate these features. I envision some people just wanting the base aaLogWebAPI while others may want SignalR and others RabbitMQ/AMQP/MQTT. It would be nice to have the ability to add plug-ins, but the notifications may require a level of integration that makes plugins difficult.
So I'm leaning towards creating a "Shared Code" project and creating separate projects for aaLogWebAPI, aaLogWebApiSignalR, aaLogWebApiAmqp, etc. Although it might be possible to abstract the notification code in order to utilize a notification plugins.
Add notifications for new log messages to subscribed clients