I read through the response on the stackoverflow and from what I know the crux of the Helix framework appears to be 'Automation of Declarative State Management for Clustered Resources' ... now isn't that a mouth-full :-)
I think any other capability with scaling etc is add-on to the core competency of Helix. On Fri, Jul 11, 2014 at 10:49 AM, Shirshanka Das <shirsha...@gmail.com> wrote: > Think about analogies to netty for network programming in Java > > > _____________________________ > From: kishore g <g.kish...@gmail.com> > Sent: Friday, July 11, 2014 10:46 AM > Subject: Re-define: What is Helix > To: <u...@helix.apache.org>, <dev@helix.apache.org> > > > Hi,This is something that has been bothering most of us. Should we callHelix > *"clustermanagement framework"*? Its a framework alright, but is it > clustermanager?- I am not sure. Cluster management is a broad term and can > meandifferent things to different people. But the most common understanding > ofcluster management term is managing a set of machines and > starting/stoppingprocesses on those machines. In other words, it cluster > management issynonymous to a deployment solution.Because of this > terminology, Helix is often compared with Mesos/YARN/Ambariand other > frameworks that manage the start/stop of processes. I haveanswered this > athttp://stackoverflow.com/questions/16401412/apache-helix-vs-yarn but > everyone i talk to ask the same question again and again. For e.g. some > oneasked if they can put together a Hadoop Cluster using Helix. Here is the > Hadoopecosystem table where Helix islabelled as system deployment.I feel the > best way to clear this confusion is re-brand Helix as somethingelse that > helps one understand what it is and when can some one use it.What do others > think. Any suggestions on what we should re-brand it as?thanks,Kishore G >
