4 ms·
This looks good, nice work. I need something like this at the moment, but I'm curious what the target company size is for a project like this. For example, we'
by dmix 11y ago
This looks good, nice work.
I need something like this at the moment, but I'm curious what the target company size is for a project like this. For example, we're a 2-3 person team and not quite big enough to have the capacity to run our own deployment of something as critical as Kala/job schedulers. Nor do I want to run another DB like Bolt/Redis when I'm already running another critical DB.
I'll probably go with a hosted solution ala http://www.iron.io/worker http://www.iron.io/worker until we can run our own.
- shazow 11y agoBolt is an in-process database, like sqlite or leveldb. And it's native-Go, so there are no dependencies. You don't need to run additional service infrastructure to use it.
- carimura 11y agoJust for clarification, the IronWorker platform by Iron.io supports large enterprise deployments in cloud, on-premises, and hybrid environments, so it scales from small hosted projects to very large deployments processing millions of jobs per hour. http://www.iron.io/enterprise/ http://www.iron.io/enterprise/
- ajvb 11y agodmix, a 2-3 person team is actually exactly what this project was built for. The use case came from a start-up of the past that I was an engineer at that really really needed something like this.
- dmix 11y agoFair enough, different teams have more resources for sys admin work or are at a later stage where they can invest in it. I'm just wary of adding any external pieces of software after being burned a few times staying up late on weekends fixing a broken service.