I was approached by a publisher the other day to do a book on Kafka - something I've actually thought about pursuing. Before I say yes (or consider saying yes), I wanted to make sure no one else was working on a book. No sense in producing competing texts at this point.
So, anyone working on a Kafka book? Self published or otherwise?
At LinkedIn, committers are too busy to write a Kafka book right now. I think this is a good idea to pursue. So, if you want to do it, we'd be happy to help. The only request that I have for you is while writing the book, it would be good if you can use this opportunity to also help us improve the documentation of the site.
On Tue, Mar 19, 2013 at 6:34 AM, David Arthur <[EMAIL PROTECTED]> wrote:
I've been thinking for a while about how to contribute to the project and thought that working on some documentation for the website might be a good way. Do you have an outline of what you'd like the site to look like that I (AND OTHERS hint, hint) could pick a topic, write the article and submit for you guys to review? Thanks,
Chris On Tue, Mar 19, 2013 at 12:20 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
Who is the target audience for the book, 0.7.2 users migrating to 0.8 or potential users of 0.8? Let me suggest a 2nd topic catering to the latter audience: getting from a dev environment (as described in the quickstart doc) to a production environment, with Zk/brokers/etc. deployed on different nodes, including replication and failover. In my experience with pitching Kafka inside 2 different companies engineers & decision makers with no first hand experience with Kafka will have a hard time buying in in absence of seeing the path all the way to production. In addition, replication and management of failures would also cater to 0.7.2 users, for whom these are new as well. Just a thought :)
On 3/19/13 2:28 PM, "Neha Narkhede" <[EMAIL PROTECTED]> wrote:
* I think it would be useful to start with a complete example (ready to copy/paste) and then break it down bit by bit * Some of the formatting is funky (gratuitous newlines), also I think 2 spaces looks nicer than 4 * In the text, it might be useful to embolden or italicize class names
Also, maybe we should move this to a separate thread?
Many thanks for contributing! The docs are very helpful. I found a couple small possible typos. The partitioning code example looks like it repeats at the bottom with duplicate import and class definition statements. Also the create topic command-line appears to have an extra '-' for the partition option. I can edit these, but before doing so I wanted to check and make sure I wasn't mistaken.
On Thu, Mar 21, 2013 at 12:42 PM, Chris Curtin <[EMAIL PROTECTED]>wrote:
I've also removed some of the unnecessary newlines.
Chris On Mon, Mar 25, 2013 at 12:04 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
Chris Curtin 2013-03-25, 16:43
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext