The ML side is split from batch, this is part of our ML infrastructure http://tech.nextroll.com/blog/data-science/2018/04/26/just-binary-classifier.html http://

The ML side is split from batch, this is part of our ML infrastructure http://tech.nextroll.com/blog/data-science/2018/04/26/just-binary-classifier.html http://tech.nextroll.com/blog/data-science/2018/04/26/just-b... . The batch usecase is, among the other things, attribution and it doesn't process 30x80B events per day, it looks at site activity and campaign activity over the past 90+ days and draws customer journey for each cookie. We obviously used to do things, when we were smaller, by keeping the data streamed in a database like hbase, but not only that was horribly slow and unreliable, it was also horribly expensive and doesn't really allow for re-applying a different attribution model retroactively and interactively like our product allows today (and it's incidentally now it's also much cheaper and faster than it used to be in the past when it was a streaming solution, orders of magnitude at that even). In any case attribution is just one of the things we do in batch, and certainly one the bigger ones.