oak
Bee-Queue
Our great sponsors
oak | Bee-Queue | |
---|---|---|
19 | 6 | |
4,994 | 3,619 | |
0.9% | 1.8% | |
9.0 | 8.5 | |
6 days ago | 2 days ago | |
TypeScript | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oak
-
Organizing large amounts of functions
Are you using Oak? If not you should check it out https://oakserver.github.io/oak/
-
Creating an NPM Package in 2024 (Deno, dnt)
oak
-
Getting Started with WebSockets in Deno: Tutorial and Examples
oak - web framework
-
Supabase Local Dev: migrations, branching, and observability
Hey @cjonas, I'm a developer on Supabase Edge Functions team. We do have plans to improve the current database trigger behavior. Will share more updates on this in the coming months.
Can you explain what do you mean by template URLs? Do you mean route params like `/v1/functions/users/:id`? If so, you can use a framework like Oak[1] to handle them. Edge Functions will make the full path including querystring available to the router.
Source maps, is it broken during local dev or when you deploy the function? Also, by broken you mean in a stack trace the file / line numbers aren't accurate?
[1] https://github.com/oakserver/oak
-
Web Fundamentals: HTML Forms
Oak framework [Website]
-
Serverless at the Edge: A Quick Overview
If you donโt want to use a full stack framework, you can develop your frontend and backend separately. With Cloudflare, you can serve your frontend and static assets with Pages or Workers Sites. With Deno Deploy, you can serve static assets from the filesystem. As for the backend, you probably want to use an HTTP framework such as Sunder (if you target Cloudflare Workers), oak, Router, or Sift (if you target Deno Deploy).
- Fresh is a new full stack web framework for Deno
-
One Hour with Deno
Oak server - middleware framework for Deno's native HTTP server. 'destjs' use it under the hood.
-
HTTPS Module Imports for NodeJS are on the way!
The issue about resources vanishing does happen, e.g. this example, meaning things like CI outages / non-deterministic builds / etc are possible, especially under a decentralized package hosting model.
-
An Introduction to Deno: Is It Better than Node.js?
Here's an example that uses Oak, a web application framework for Deno, to create a basic web server:
Bee-Queue
-
Node.js backend architecture question
You could use a Redis based job system like https://github.com/bee-queue/bee-queue for maintenance and email. The jobs could be populated by the API service, some cron scripts, and whatever else, while you'd have dedicated worker processes (written in Node.js?) pulling the jobs and running them.
-
Building a task queue, Part 1
The Node.js libraries BullMQ and Bee Queue are also infrastructure and interface. However, you typically have to use their interface.
-
Scaling synchronous microservices
I'm a fan of bee-queue for this when working in Node, but it's just a wrapper around reliable queue patterns in Redis; you might want to investigate how it works (the readme is quite good) for your own use case, or find an equivalent for your environment. The key is it's designed for short tasks (seconds long, not minutes or hours), and you can receive a result back from the task unlike some fire-and-forget queueing solutions.
-
[Question] API routes and worker_threads
I'd also consider something like bee-queue, which would enable you to scale across processes or even across multiple server machines.
-
NodeJS recommended job queue/message queue??
For NodeJS, there are BullMQ(successor of Bull), Bull and Bee Queue
-
[AskJS] How do you do JS on the backend?
bee-queue for offloading tasks onto non-web-server machines
What are some alternatives?
Express - Fast, unopinionated, minimalist web framework for node.
bull - Premium Queue package for handling distributed jobs and messages in NodeJS.
opine - Minimalist web framework for Deno ported from ExpressJS.
kue - Kue is a priority job queue backed by redis, built for node.js.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript ๐
Qedis
Koa - Expressive middleware for node.js using ES2017 async functions
The gist - BullMQ - Message Queue and Batch processing for NodeJS and Python based on Redis
Deno.watchFs - Tracking the behavior of Deno.watchFs on different systems
node-resque - Node.js Background jobs backed by redis.
node-express-boilerplate - A boilerplate for building production-ready RESTful APIs using Node.js, Express, and Mongoose