Dalga: Job scheduler written in Go • Hacker News Board

Re: Dalga: Job scheduler written in Go

#11

Post by mystique » Wed, Aug 12, 2015, 2:40 PM UTC

Have you looked at Rundeck? http://rundeck.org/

It has rest based interface to do everything + UI to make it easier when you need to do one off things. It allows you to control execution across multiple nodes. Good thing is you can setup your processes by tag of a node in Dev and export the project as is on Production and it will still work.

It's a runbook automation tool but can be used like in place of chronos, oozie, spark job server etc.

Re: Dalga: Job scheduler written in Go

#12

Post by jerf » Wed, Aug 12, 2015, 2:54 PM UTC

cenkalti wrote: post #6

rbanffy wrote: post #2

Why Dalga instead of plain cron?

* Dalga stores jobs in a MySQL table which is handy if you are already using MySQL (backups, etc.) * Dalga can schedule one-off jobs. * Dalga has built-in retry mechanism.

A tight dependency on MySQL is somewhat limiting. Have you considered making that an interface with a default implementation that uses MySQL? It pretty much ought to be a mechanical transform where you simply extract all the places you touch MySQL into a method, then write an interface around that method.

Re: Dalga: Job scheduler written in Go

#13

Post by jksmith » Wed, Aug 12, 2015, 3:19 PM UTC

Why Dalga instead of of some other job scheduler? Because all service software will eventually be rewritten in golang, apparently ;). Don't hate the player.

Re: Dalga: Job scheduler written in Go

#14

Post by wilsonfiifi » Wed, Aug 12, 2015, 3:41 PM UTC

jksmith wrote: post #13

Why Dalga instead of of some other job scheduler? Because all service software will eventually be rewritten in golang, apparently ;). Don't hate the player.

To be honest, I like the fact that a lot of the 'old` stuff is being rewritten in Go because I find it a much easier language to grasp than C, C++ or Java. So I say rewrite them all! (just my opinion of course)

Re: Dalga: Job scheduler written in Go

#15

Post by coverband » Wed, Aug 12, 2015, 8:32 PM UTC

cenkalti wrote: post #5

x0rg wrote: post #3

Why Dalga instead of Kala? https://news.ycombinator.com/item?id=10046164 Aren't they very similar? Isn't it better to join the efforts?

Kala is in Alpha stage. Dalga is stable and used in production ~2 years at https://put.io .

On a completely different note, kudos for the idea of charging a small amount that gets contributed to charity for trial accounts (on https://put.io/).

Not sure if you guys came up with that, but it's the first instance I've come across. Great idea -- filters out freeloaders from potential true customers.

Re: Dalga: Job scheduler written in Go

#16

Post by jksmith » Wed, Aug 12, 2015, 9:59 PM UTC

wilsonfiifi wrote: post #14

jksmith wrote: post #13

Why Dalga instead of of some other job scheduler? Because all service software will eventually be rewritten in golang, apparently ;). Don't hate the player.

To be honest, I like the fact that a lot of the 'old` stuff is being rewritten in Go because I find it a much easier language to grasp than C, C++ or Java. So I say rewrite them all! (just my opinion of course)

Well that's a driver for golang for sure. Additionally, while we're complaining about golang not measuring up to our programming sensibilities, the people who write us checks want 1) correct, 2) on time, and 3)in budget. If golang helps us do that better than other languages in spite of the fact that it doesn't have generics or whatever (anecdotally seems to be the case), no need to apologize for it.