You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ekaf has now crossed 70 stars, and averages over 100 clones every week.
In the spirit of the open source community, please drop a comment if your company uses ekaf in production. Any additional information you can provide will be greatly appreciated.
This will particularly be useful when anyone gives a talk about ekaf and erlang/kafka, and in turn getting more active participation and interest in using and evolving ekaf.
At Helpshift, we push around 300 million events every day to our events topic that contains 4-5 partitions. Kafka (4-5 brokers) has been solid as a rock and the central glue across 100's of repos/micro-services written across erlang, golang and clojure. It has also helped that ekaf can (& has) provided the offline backup & replay functionality. The metrics are something that has particularly delighted our ops team - info about distribution among partitions, buffer size when flushed, broker/partition intermittent downtime are all possible by adding callbacks that push to statsite/graphite.
And last but not least, many thanks to @ghoseb (CTO at Helpshift) & my colleagues @helpshift for allowing ekaf to be written in erlang, reviewing, QA'ing, debugging, and deploying ekaf.
Feel free to share how you use ekaf or submit a talk of your own.
I am considering submitting a talk on how ekaf is used by the community, and perhaps its internals.
ekaf has now crossed 70 stars, and averages over 100 clones every week.
In the spirit of the open source community, please drop a comment if your company uses ekaf in production. Any additional information you can provide will be greatly appreciated.
This will particularly be useful when anyone gives a talk about ekaf and erlang/kafka, and in turn getting more active participation and interest in using and evolving ekaf.
At Helpshift, we push around 300 million events every day to our events topic that contains 4-5 partitions. Kafka (4-5 brokers) has been solid as a rock and the central glue across 100's of repos/micro-services written across erlang, golang and clojure. It has also helped that ekaf can (& has) provided the offline backup & replay functionality. The metrics are something that has particularly delighted our ops team - info about distribution among partitions, buffer size when flushed, broker/partition intermittent downtime are all possible by adding callbacks that push to statsite/graphite.
We use https://github.com/lpgauth/statsderl by @lpgauth, a prolific erlang contributor to push metrics. ekaf's dependency include @uwiger 's https://github.com/uwiger/gproc. Our tests uses @ninenine's https://github.com/ninenines/ranch to mock a kafka broker.
Hat-tip & thanks to those in all in community who have raised issues, cloned or favourited the ekaf repo including in no particular order @WanliTian (ekaf's most recent contributor from Baidu) @qrilka @mitchellwrosen @vglukhovskiy @RomanShestakov @jccampagne @belltoy @chengat1314 @cybergrind @dbdn @ericliang @gaynetdinov @harekumar @jwilberding @kachayev @layerhq @linearregression @mubarak @sagelywizard @joestein @a13x @sdanzan @smarin @wrw @xwiz @ysantos @zhangxinrun @xpd54 @ates @flyjack @wdshin @sipims @thatJoeGuy16 @ameensol @mjs2600 @shabankarumba @Lavrin @vamsimokari
And last but not least, many thanks to @ghoseb (CTO at Helpshift) & my colleagues @helpshift for allowing ekaf to be written in erlang, reviewing, QA'ing, debugging, and deploying ekaf.
Feel free to share how you use ekaf or submit a talk of your own.
I am considering submitting a talk on how ekaf is used by the community, and perhaps its internals.
Kafka Summit is happening in April 2016 in San Francisco
More at http://kafka-summit.org
Hope to see you there. And thank you for the continued encouragement and support.
The text was updated successfully, but these errors were encountered: