Onyx 0.6.0: Going Faster
michaeldrogalis.github.io
Onyx 0.6.0: Going Faster
1–10 of 14 posts
Re: Onyx 0.6.0: Going Faster
#2Re: Onyx 0.6.0: Going Faster
#3Re: Onyx 0.6.0: Going Faster
#4"Based on user feedback, Kafka seems to be the the primary means that developers are interested in ingesting data from. We rewrote the onyx-kafka plugin from scratch to essentially mirror what Storm's Kafka Spout provides. That is, the Onyx Kafka plugin will dynamically discover brokers from ZooKeeper and automatically reconnect to an In Sync Replica (ISR) if any brokers go down. We also took a little detour to create onyx-s3. onyx-s3 is an S3 reader that handles faults by check-pointing to ZooKeeper."
Re: Onyx 0.6.0: Going Faster
#5It seems to me this will replace Storm for many uses, and it seems they knew this and they've been putting effort into taking on exactly that sort of use case: "Based on user feedback, Kafka seems to be the the primary means that developers are interested in ingesting data from. We rewrote the onyx-kafka plugin from scratch to essentially mirror what Storm's Kafka Spout provides. That is, the Onyx Kafka plugin will d…
Re: Onyx 0.6.0: Going Faster
#6Re: Onyx 0.6.0: Going Faster
#7Who is using Onyx?
Re: Onyx 0.6.0: Going Faster
#8Really excited to see where this project goes. Has the best "to production" story I've seen from any of the batch/streaming frameworks.
Re: Onyx 0.6.0: Going Faster
#9In another thread recently, someone mentioned that Phoenix wasn't a good name choice for a project because its been used so many times. I feel like Onyx is the same way. This thing might displace the other Onyxes for a while only to be lost to history when some other software project eventually is also called Onyx.