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
by jlouis on Wednesday August 12, 2015 @06:53AM
(#10047081)
In large setups, it is usually clever to isolate job execution policy into a separate system. This simplifies a lot of contextual configuration of the system at large.
You can have cron emit the cascading event if you want but you often need a system which can "prod" other systems and ask them to do things because of a timing event. In such systems, cron often falls short as the system around it grows.
For local timing of events, cron is a really good tool however, and I wouldn't hesitate about using it there. It is for system-wide events these general job schedulers tend to help.
Re:Dalga: Job scheduler written in Go
by jerf on Wednesday August 12, 2015 @10:54AM
(#10048006)
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
by jksmith on Wednesday August 12, 2015 @11:19AM
(#10048175)
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
by wilsonfiifi on Wednesday August 12, 2015 @11:41AM
(#10048315)
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
by jksmith on Wednesday August 12, 2015 @05:59PM
(#10050958)
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.
Re:Dalga: Job scheduler written in Go
by coverband on Wednesday August 12, 2015 @04:32PM
(#10050422)
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.
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.
You can have cron emit the cascading event if you want but you often need a system which can "prod" other systems and ask them to do things because of a timing event. In such systems, cron often falls short as the system around it grows.
For local timing of events, cron is a really good tool however, and I wouldn't hesitate about using it there. It is for system-wide events these general job schedulers tend to help.
* Dalga can schedule one-off jobs.
* Dalga has built-in retry mechanism.
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.