Batch tasks query data from InfluxDB and Stream tasks process data that is
directly sent to Kapacitor. i.e pull vs push
There are some highlevel differences with batch and stream
Batch:
Higher latency on processed data since you have to wait to the query
to be scheduled.
Can access data from wide ranges of time
Stream
Lower latency since the point is processed as soon as it arrives
Limited by available RAM so it cannot work with large ranges of time.
For example using a stream task to compute the mean over a 24 hour period
is not a good idea since 24h of data would need to be stored in RAM.
In most cases any batch task can be converted to a stream task and vice
versa, which you use depends on your latency and RAM requirements.
On Thursday, November 3, 2016 at 8:39:39 AM UTC-6, amith...@gmail.com wrote:
>
> Hi All,
>
> Apologies for noob questions, I am new to TICK architecture.Could you
> please help me understand how stream is different in working from batch.
> What are all the situation when we should use batch and stream respectively.
>
> Thanks.
>
>
--
Remember to include the version number!
---
You received this message because you are subscribed to the Google Groups
"InfluxData" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to influxdb+unsubscr...@googlegroups.com.
To post to this group, send email to influxdb@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit
https://groups.google.com/d/msgid/influxdb/a27cdb57-88e1-48da-a6a0-8634ace1ea57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
