search

mreinstein / node-gearman

⚙ Gearman client and worker for node
75 stars 13 forks source link

Updates #14

Closed rafacustodio closed 10 years ago

rafacustodio commented 10 years ago

This project still has updates?

http://gearman.org/news/ <- The last update was in september of 2013, for big companies should I be worried?

mreinstein commented 10 years ago

@rafael-custodio I'm still updating the project, but it's pretty much complete; supports the full gearman protocol as far as I'm aware. I don't think gearman is popular anymore but it's still usable. So I'm maintaining this library for people that still use it.

mreinstein commented 10 years ago

what updates are you looking for on this project?

rafacustodio commented 10 years ago

Well, I used it a little bit and realized that is pretty much complete, it's complete with the latest gearman, but the latest gearman is already old, I'm using gearman for some time now and I process more than 1 million requests per day on it, we are developing the new version of our platform using zend 2 along with angularjs and node (for notification), the tasks part I was thinking in transfer all to node, because it's asynchronous and is going to make the tasks even faster, but the reason that gearman is old is worrying me, using and old thing in a new version of the plataform is not the way, but I use the uniqueIds from gearman (it's a lot of requests per seconds and that can duplicate), and o saw that rabbitmq doesn't have that, so now I'm between gearman or redis queue, because the beanstalkd is old as well.

I saw this https://github.com/LearnBoost/kue for redis, it's kind of interesting, but still the same problem with unique ids.

Your project is really good, and I would be able to safely transfer the php workers to node, thanks for that.

Sorry about my english.

rafacustodio commented 10 years ago

Well, seems like they still updating the gearman https://launchpad.net/gearmand, but why is gearman not popular anymore? Is there other better than gearman that I could use and has support to uniqueIds?

rafacustodio commented 10 years ago

I found 1 update.. is there a way to kill 1 or n workers through the node?

mreinstein commented 10 years ago

@rafael-custodio yeah gearman's popularity is on the decline, I think there are a lot of other systems that have become more popular as a replacement (redis, node, https://github.com/substack/dnode, etc)

I'm mostly just maintaining this library for people that are still using gearman and want a nice, simple library.

I found 1 update.. is there a way to kill 1 or n workers through the node?

I'm not sure what you mean. Can you explain what you're trying to do?

rafacustodio commented 10 years ago

Let's say that I configure to execute 5 workers inside the app, but later I want 4 workers, how can I kill this 1 worker inside the app?

mreinstein commented 10 years ago

you could close the connection for that worker, then you'd be able to cleanup the object. For example:

worker = new Gearman '127.0.0.1', 4730

# ... do some stuff with the worker

# cleanup
worker.close()
delete worker
mreinstein commented 10 years ago

Since I haven't heard back I'm considering this resolved. If you're still having the problem feel free to re-open.