Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno Cron

deno.com

Post reply on HN
Print view View original

41–50 of 190 posts

Re: Deno Cron

#41

Post by TheIronYuppie »

aleksiy123 wrote: post #16

Nice, I was just wondering if there was an opportunity for a product similar to vercel for batch jobs. This isn't quite that but close. From my experience there 5 main components for larger scale system. - Request server - database - queue - background worker - offline batch jobs I feel like so far serverless has the first 3 fairly well developed but the last two are still underdeveloped. But maybe I'm just not aware…

This is really interesting - we’ve tried really hard to solve some of these with Bacalhau[1] - a much simpler distributed compute platform. Would love your feedback!

[1] https://github.com/bacalhau-project/bacalhau

Disclosure: I confounded Bacalhau

Re: Deno Cron

#42

Post by slig »

aleksiy123 wrote: post #16

Nice, I was just wondering if there was an opportunity for a product similar to vercel for batch jobs. This isn't quite that but close. From my experience there 5 main components for larger scale system. - Request server - database - queue - background worker - offline batch jobs I feel like so far serverless has the first 3 fairly well developed but the last two are still underdeveloped. But maybe I'm just not aware…

You should check Windmill.dev.

Re: Deno Cron

#43

Post by mike_d »

vvpan wrote: post #37

I am a lead on a small startup team and one of the biggest pain points is dealing with infrastructure. We have no dedicated devops person and much of that work falls on me and other people who would be better writing code. I think the cloud paradigm is experiencing a shift. Few of us want to deal with cloud infrastructure (whether clicking around or via Terraform or equivalent) to execute a function every X minutes -…

It is really disappointing to me when I hear takes like this. As an industry we are splitting the roles of programmers and engineers so that programmers can just throw spaghetti at the wall and it is the engineers problem to happily run it.

We need more well rounded people that also fundamentally understand how their code is executing on the backend so performance and cost can be optimized.

Re: Deno Cron

#44

Post by vorticalbox »

lucacasonato wrote: post #20
obblekk wrote: post #19

How long does the job get to run? Would be really awesome if this could be used to offload long lived jobs from the request. Defer.run is building this for vercel and it’s really cool.

You can use Queues for this :) https://deno.com/blog/queues

I wish this had a built in rate limit, I wanted to hit an api with lots of test data, I didn't need to actually wait for the response and I didn't really care how long they took.

I just needed to limit how fast the http requests went.

I guess I could do this with the delay and calculate how long it would need to wait.

Re: Deno Cron

#46

Post by igorzi »

nwjsmith wrote: post #30
lambtron wrote: post #2

hey, andy from the deno team here. we're really excited to land this. happy to answer any questions or pass questions along to the team!

Is the spikiness of cron schedules going to cause you operational problems? You're going to end up with a _lot_ of jobs scheduled at "0 0 * * *".

Yes, we're anticipating more spiky workloads because of this. Deno Deploy is already designed to handle spikes, but we also have a few additional mitigations in place for Cron. For example, we will limit concurrent dispatches for the same project/user/organization, which may slightly delay the execution of specific cron tasks.

Re: Deno Cron

#47

Post by dyeje »

vvpan wrote: post #37

I am a lead on a small startup team and one of the biggest pain points is dealing with infrastructure. We have no dedicated devops person and much of that work falls on me and other people who would be better writing code. I think the cloud paradigm is experiencing a shift. Few of us want to deal with cloud infrastructure (whether clicking around or via Terraform or equivalent) to execute a function every X minutes -…

There’s a new crop of PaaS products that aim to provide a layer of sanity on top of cloud providers (e.g. Aptible). Might be a good fit for you.

Re: Deno Cron

#48

Post by marcosdumay »

mike_d wrote: post #43
vvpan wrote: post #37

I am a lead on a small startup team and one of the biggest pain points is dealing with infrastructure. We have no dedicated devops person and much of that work falls on me and other people who would be better writing code. I think the cloud paradigm is experiencing a shift. Few of us want to deal with cloud infrastructure (whether clicking around or via Terraform or equivalent) to execute a function every X minutes -…

It is really disappointing to me when I hear takes like this. As an industry we are splitting the roles of programmers and engineers so that programmers can just throw spaghetti at the wall and it is the engineers problem to happily run it. We need more well rounded people that also fundamentally understand how their code is executing on the backend so performance and cost can be optimized.

We need decently designed environments where running stuff is trivial. It's not practical to expect the same person to be able to deal with both all the bullshit that comes from making the spaghetti and all the bullshit that comes from making it adhere to the wall.

Re: Deno Cron

#49

Post by klabb3 »

vvpan wrote: post #37

I am a lead on a small startup team and one of the biggest pain points is dealing with infrastructure. We have no dedicated devops person and much of that work falls on me and other people who would be better writing code. I think the cloud paradigm is experiencing a shift. Few of us want to deal with cloud infrastructure (whether clicking around or via Terraform or equivalent) to execute a function every X minutes -…

> 1. Services like this cron with Dyno Deploy or Vercel where the cloud things are abstracted away for you.

I agree with the sentiment, but to me it’s a shame this even qualifies as abstraction in the first place. Periodic execution of a function is extremely basic and already exists in almost every programming environment. If this needs to be a service (instead of a library call), there is something deeply wrong elsewhere, imo. We all laughed about leftpad, but at least that was native code and not “as-a-service”, dependent on networking and proprietary code on someone else’s machine.

I have nothing against Deno in particular, and I’m also not saying this is easy from an implementation perspective (due to complexity elsewhere). I’m just surprised that trivial features – from an end-user perspective – justify such a ruckus.

Re: Deno Cron

#50

Post by conradfr »

vvpan wrote: post #37

I am a lead on a small startup team and one of the biggest pain points is dealing with infrastructure. We have no dedicated devops person and much of that work falls on me and other people who would be better writing code. I think the cloud paradigm is experiencing a shift. Few of us want to deal with cloud infrastructure (whether clicking around or via Terraform or equivalent) to execute a function every X minutes -…

For cron jobs in Elixir you can use:

- [0] Quantum, quite simple and supports cron syntax.

- [1] Oban, which is a job runner, requires a DB, but also supports periodic jobs with a cron syntax.

(probably others but that's the ones I've used)

[0] https://github.com/fanduel/quantum-elixir

[1] https://github.com/sorentwo/oban

Post reply on HN