Taskless.io

Easy job queuing for serverless deployments

➡️ Federated from @[email protected]
🔕 Replies on Twitter not monitored

[Taskless.io @gotaskless]

https://t.co/L2Ym8IwUW6 is the easiest way to add job queues and background tasks to your serverless apps, with built-in support for popular JS frameworks.

Early Access is available! -- https://t.co/WOzkwp5hkq

[Taskless.io @gotaskless]

improvements to the MongoDB driver including better write retry support & idempotent sorting

#DocMQ #MongoDB #PostgreSQL #JavaScript #TypeScript #JobQueue
https://t.co/d1vsxLhoeN (2/2)

[Taskless.io @gotaskless]

RT @[email protected]
DocMQ 0.5.6 is released! 🚀
https://t.co/Vs7qupZTL1

✨ New: A context object is available, allowing you to implement rich tracing behaviors, hook DocMQ up to #Sentry, and persist a logging object through the job's lifecycle

🔧 Fixes: Multiple (1/2)

[Taskless.io @gotaskless]

team Taskless. (2/2)

[Taskless.io @gotaskless]

We’ve been quiet over here, but only because all our energy went into the new https://t.co/WOzkwpmSJ0 home page. (Follow up has what we’re working on and what’s next)

🚀 Access is available after a quick typeform, just so we can keep a handle on capacity planning as a (1/2)

[Taskless.io @gotaskless]

And if you’ve made it to here, thank you. There’s just the two of us, but we truly believe in the idea of helping other b2c/b2b go faster with less ops overhead.

Boosts and shares are always appreciated, but just coming with us for the ride will always be enough.

With ❤️, (1/2)

[Taskless.io @gotaskless]

keys during development.

Finally there’s the whole process of transitioning out of bootstrapping. With most of the SF Bay Area returning to in-person meetings for everything, there’s a LOT of coffee in our future. ☕️ (2/2)

[Taskless.io @gotaskless]

we’re based in California. Given Delaware’s emphasis on corporate law, it’s why you see so many companies incorporate there. (2/2)

[Taskless.io @gotaskless]

bootstrapped company

📚 Docs! And guides! Some of the most common use cases for a job system on #vercel / #netlify are now covered

💰 True #serverless pricing with scale-to-zero. Slab pricing is predictable, but isn’t serverless (2/2)

[Taskless.io @gotaskless]

etc, you add another branch or set of branches to a decision tree.

This is NOT a bad thing, but it is a reason that I am resistant to customization. Each knob you add expands software complexity and room for bugs.

Source: https://t.co/bKKxfmQsia
https://t.co/NVUFdDbGkw (2/2)

[Taskless.io @gotaskless]

RT @[email protected]
This is an image of the decision tree that Slack used 5 years ago to determine whether to notify someone.

Every time you add a customization option like "don't notify me during these times in my time zone" or "mute notifications in this thread" (1/2)

[Taskless.io @gotaskless]

dependencies
- Minor doc/typo improvements

https://t.co/0Nji1n0UGF

#OSS #Release (2/2)

[Taskless.io @gotaskless]

Alright, #Taskless client v3.6.2 is out and on npm + GitHub. It's some small docs and deps changes, including the latest #DocMQ client with context support.

📃 Summary of Changes
- No longer using appId/secret pairs and those deprecated paths are removed
- Updated (1/2)

[Taskless.io @gotaskless]

RT @[email protected]
I've been working today on a tool to benchmark the loading of a ESM module graph in Node. I'm using the Chrome Tracing as a profiling frontend #nodejs #chrome #javascript
https://t.co/FLpDLk32Lr

[Taskless.io @gotaskless]

✨ Failure Alerts - Catch job errors before they impact your users. Should your serverless job fail too often, Taskless will send you an email so you can triage, act, and respond from anywhere.

[Taskless.io @gotaskless]

It's just databases?
Always has been. 🌏👨‍🚀🔫👨‍🚀

[Taskless.io @gotaskless]

Taskless 2.1.0 is now available via npm. Serializable stack traces, zero-request startup for the dev server, and more. Full changelog @ https://t.co/yoGmxHbLr3

[Taskless.io @gotaskless]

The Taskless integrations make it easy to do background processing on the edge. (1) Create the queue, (2) Write the handler, (3) call enqueue() somewhere else and let Taskless do the rest; about 8 lines of code.