News for hackers. Stuff that matters.
Re:Show HN: Goka – distributed stream processing library for... by malandrew on Wednesday May 17, 2017 @06:29PM (#14363375)
Anyone interested in this should check out Uber's Cherami, which has support for go, java and python:

http://eng.uber.com/cherami/

https://github.com/uber?utf8=%E2%9C%93&q=cherami&type=&langu...

It supports consumption of kafka topics:

https://github.com/uber/cherami-server/commit/226fb2c55b7c51...

Re:Show HN: Goka – distributed stream processing library for... by u320 on Wednesday May 17, 2017 @05:22PM (#14362912)
Why would anyone want to use this over Kafka Streams? Seems a lot more verbose.
Re:Show HN: Goka – distributed stream processing library for... by fdsfsafasfdas on Wednesday May 17, 2017 @05:43PM (#14363069)
Perhaps because they would like to call into code written in Go.
Re:Show HN: Goka – distributed stream processing library for... by ah- on Wednesday May 17, 2017 @05:42PM (#14363066)
No Kafka Streams for Go yet.
Re:Show HN: Goka – distributed stream processing library for... by jaytaylor on Wednesday May 17, 2017 @08:43PM (#14364055)
re: yet

Is the work in progress? If so, please tell us where.

Re:Show HN: Goka – distributed stream processing library for... by alexott on Wednesday May 17, 2017 @10:17PM (#14364405)
As I remember, they said that tgey want to stabilize API before adding support for new languages
Re:Show HN: Goka – distributed stream processing library for... by 0xdb7 on Thursday May 18, 2017 @04:31AM (#14365679)
Goka is not a replacement for Kafka Streams, they can be used together. For example, you can use streams and tables created with Kafka Streams inside services built with Goka.
Re:Show HN: Goka – distributed stream processing library for... by agnivade on Friday May 19, 2017 @06:38AM (#14374318)
How does this compare with https://github.com/movio/kasper ?
Re:Show HN: Goka – distributed stream processing library for... by 0xdb7 on Friday May 19, 2017 @09:44AM (#14375522)
There are several differences. Here are some of them.

- Kasper is micro-batched, Goka consumes one message at a time.

- Kasper requires a centralized state storage (such as Redis or ElasticSearch), Goka only depends on Kafka: processors persist their state (key-value tables) in a compacted topic in Kafka. That is really nice because processors can then join streams with tables of other processors.

- Kasper statically assigns partitions to processors. Goka automatically splits the input and state partitions among processors.

- By default Goka employs sarama and sarama-cluster libraries to access Kafka, but that can be easily replaced with Confluent's go library. Similarly, the local storage is by default LevelDB, but can be replaced even with some remote storage if necessary.

Re:Show HN: Goka – distributed stream processing library for... by wubal on Wednesday May 17, 2017 @11:03PM (#14364552)
Happy to see a Go alternative.. Good job OP