Re:Show HN: Upstream – Stream processing, for humans
by dozzie on Thursday April 27, 2017 @07:20AM
(#14210652)
So your service basically provides (a) place where one can send data for
further processing, (b) place where one can process data that was collected,
(c) tools for plotting and charting available data, and (d) tools for sending
alerts on available data. And registry with available data streams.
Mind you, access control is most probably not a feature for your customers,
but for your company. Limiting data visibility for employees is usually
unnecessary for smallish businesses, and big businesses rarely take part in
developing somebody else's product like this.
With all this, I would say that you are like AMQP broker, except you have
a stream registry, can do a little of trivial data processing (handful of set
functions on a window), have a charting UI, and no way of extracting data
back, from what I've seen in the documentation.
And you asked what I compare your service with. These would be Splunk and
Riemann from finished software, and in terms of processing capabilities,
plenty of stream processing systems invented in academia, like Aurora.
Mind you, access control is most probably not a feature for your customers, but for your company. Limiting data visibility for employees is usually unnecessary for smallish businesses, and big businesses rarely take part in developing somebody else's product like this.
With all this, I would say that you are like AMQP broker, except you have a stream registry, can do a little of trivial data processing (handful of set functions on a window), have a charting UI, and no way of extracting data back, from what I've seen in the documentation.
And you asked what I compare your service with. These would be Splunk and Riemann from finished software, and in terms of processing capabilities, plenty of stream processing systems invented in academia, like Aurora.