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

Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 114 posts

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#31

Post by fswd »

Why a company with VC backing for something so simple? I am confused why somebody would think this is so important, they would need funding. Anybody with 1-2 years development experience should be able to hack something up in redis or even just crontab and flag files.

I use postgraphile graphile-worker https://github.com/graphile/worker for this.

For example, every month we roll over credits. For each user, when they signed up, 30 days from that, check. If they are available for roll over, reset and email. Then we have drip campaigns for alerts like running low on credit.

Also, if you upgraded your account, then pause payment, it uses a worker to schedule the date they are paid up to run the SQL to downgrade. With a simple API called 'addJob' that looks for a JavaScript file in a folder called task.

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#34

Post by revskill »

fswd wrote: post #31

Why a company with VC backing for something so simple? I am confused why somebody would think this is so important, they would need funding. Anybody with 1-2 years development experience should be able to hack something up in redis or even just crontab and flag files. I use postgraphile graphile-worker https://github.com/graphile/worker for this. For example, every month we roll over credits. For each user, when they…

Because i guess you've never been worked in a company with VC backing ;)

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#35

Post by benatkin »

andrewmcwatters wrote: post #33
g_delgado14 wrote: post #32

Your logo is awfully-close to sequoia capital's logo: https://www.sequoiacap.com/

Sequoia: Up and to the right Defer: Down and to the right Not a good look. Calling it now.

Either you're mistaken or that's the quickest ninja-edit I've ever seen.

Sequoia's has a diagonal line through it. Defer's does not.

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#36

Post by wittydeveloper »

bluelightning2k wrote: post #4

If we all have at least one cloud, why would we seperate out this one piece and run it in Defer instead? I don't mean to be unkind it's a legitimate question not sarcasm. It just seems like a subset of Cloud Functions or a subset of Lambda - without being connected to the rest or any of our existing workflow, monitoring, secrets, etc.

We primarily focus on helping Node.js developers to build products without investing time in infrastructure while keeping it configurable.

As @thdxr mentioned, our goal is also to provide top-notch queueing/scheduling features that are complicated to achieve with Lambda/SQS/Cloud Functions, such as dead letter queue support, throttling, or a product-oriented dashboard. In the same idea, we plan to provide better integration, for example, as you mentioned on secrets management by integrating with Doppler, AWS Secrets Manager, and more - the same goes with linked deployment pipelines.

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#37

Post by johtso »

gearnode wrote: post #24
johtso wrote: post #23

Earlier quoted context omitted.

Often you want to specify your own unique id based on some property of the job, like a transaction reference, or just a unique combination of parameters. This means you can later refer to it without having to store the reference somewhere. Is this possible?

We specify our unique ID based on KSUID specifications. In addition, we are soon releasing the tag feature, which will enable you to store your references on your Defer executions to identify them your way.

Just ideally the dev experience should be `result = await somethingThatMayHaveBeenCalledBefore(id=txnref, params)`

You shouldn't need to first do a check to see if the task already exists using a different api, and then choose whether or not to run a new task.

At least this is my preference.. a-la Durable Objects.

If you don't specify a custom unique id when calling the task it would then be treated as a task that can (and would make sense to be) run multiple times (i.e. not idempotent).

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#38

Post by andrewmcwatters »

fswd wrote: post #31

Why a company with VC backing for something so simple? I am confused why somebody would think this is so important, they would need funding. Anybody with 1-2 years development experience should be able to hack something up in redis or even just crontab and flag files. I use postgraphile graphile-worker https://github.com/graphile/worker for this. For example, every month we roll over credits. For each user, when they…

Pointing Rick Dalton This is the bookmark comment.

Something something Dropbox, something something rsync.

Charly, Bryan consider yourself flattered.

Re: Launch HN: Defer (YC W23) – Zero-infrastructure background jobs for Node.js

#39

Post by andrewmcwatters »

benatkin wrote: post #35
andrewmcwatters wrote: post #33

Earlier quoted context omitted.

Sequoia: Up and to the right Defer: Down and to the right Not a good look. Calling it now.

Either you're mistaken or that's the quickest ninja-edit I've ever seen. Sequoia's has a diagonal line through it. Defer's does not.

I'm teasing of course. :)
Post reply on HN