telescope
bull
Our great sponsors
telescope | bull | |
---|---|---|
335 | 50 | |
92 | 15,039 | |
- | 1.0% | |
6.6 | 6.8 | |
28 days ago | 3 days ago | |
JavaScript | JavaScript | |
BSD 2-clause "Simplified" 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.
telescope
-
Breaking Telescope
It all starts with an old 400 error that was occurring in Telescope for a while now, first documented here.
-
Starchart: Choosing a technology
Sattelite for the back end
-
Choosing a path
There are a few places to start with this, one is that we have an issue in Telescope that relates to what I think is the session no longer existing in certain situations that results in a 400. This will give me an opportunity to take a look at Telescopes auth flow. I still am kind of unfamiliar with Telescope despite having been in the last OSD course. I know that we use passport SAML in Telescope however and in the new project we will use a different library called SAMLIFY.
-
Planning: Using Satellite features in Starchart
The project is currently in the planning phase, and being part of the development team, I have been researching ways to add relevant bits of Satellite in the Remix Blues Stack project, we intend on using for Starchart.
-
Telescope: How I set it up
As a good well-established project, Telescope provides a great environment setup guide, which covers most use cases.
-
Spying on Starchart
It's been a year since I was supposed to work on Telescope for a class. When the war in Ukraine started in February 24th, 2022, I almost fully stopped contributing. Now, this year I am trying to do more, even though it's not my class anymore. Because I wish that I did more back then.
-
Setting up Telescope
This week, I decided to setup Telescope locally. I had previously contributed to telescope and had set it up already. However, I faced some problems starting it up locally after a shutdown and startup sequence. This was hard to debug since there was no error message, just containers on docker would not start up even after waiting for several minutes. These problems would fix after a restart or just randomly after a few tries. So, I decided to go through the setup again.
-
Setup for Telescope
Task This week, I try to revisit my setup for running the Telescope project, a single page website that aggregates blog posts.
-
Telescope -filtering feed URLs - release
This week, I finished implementing the feature for filtering out irrelevant feed URLs. Previously, I had added a function for the filtering but had to write the test for it.
-
Patching It Up, Part 3: Release
The two PRs(1 2) mentioned last time were merged without a hitch. For the one that's about parsing Twitch channel feed URL, the maintainer and I agreed that there should be a follow-up issue opened to expand it to YouTube Channel(s). They also found another bug in the sign-up that should exist as its own issue about the RSS feed URL(s) having incorrect domain. For details about them, please see my last post.
bull
-
Prioritizing Concurrent Requests: Queuing system to handle distributed processes and messages with NodeJS and Bull
To implement the solution with a queue, I used a package called 'Bull' (https://github.com/OptimalBits/bull). It's a library that helps with distributed job control, providing some very useful solutions for this type of work, such as background job processing, queues with priorities (FIFO, LIFO, and others), among other features. 'Bull' uses Redis for queue storage, so if your application crashes for any reason, once it's back online, it will continue executing the processes that are in the queue. In our case, we'll use the FIFO (First in, first out) queue solution, meaning priority based on arrival order.
-
Instrumentation for Event Driven
We use bull-js for our distributed queue and event-driven library.
-
Redis master/slave setup on Kubernetes throwing error: BRPOPLPUSH { ReplyError: MOVED 2651
I'm using the excellent Redis based Bull.js as a job queue on Kubernetes.
-
How to use Job Queue to handle email sending in your Nestjs server
For Job Queue, NestJs provides a package named @nestjs/bull as an abstraction/wrapper on top of Bull, a popular, well-supported, high-performance Node. js-based Queue system implementation.
-
How do you handle queues in Node.js? Have you ever tried using pgboss?
I'm working on a large ETL project that involves handling queues for file integration. Currently, we are using Redis with Bull (https://www.npmjs.com/package/bull) for this purpose. However, to streamline our architecture and address security concerns, we are considering migrating the queue to PostgreSQL.
-
What is a good background scheduler?
BullMQ is a pretty solid choice: https://github.com/taskforcesh/bullmq It's the successor of Bull: https://github.com/OptimalBits/bull
-
Learning Guidance
For Node specifically, things like Streams, understanding the asynchronous model completely, and the event loop. Also, queues tend to get used a lot in Node, so understanding the basic concepts behind that and how to use something like bull would be useful.
-
image processing in express application, should it be done in a separate thread?
To do this properly, you need to put the task into queue, so if there are 1000 simultaneous uploads it won't kill your server but will be processed one by one. For the queue, see bull. Image hostings like AWS have some functionality for processing on their side, as an option.
- Best development practice for setting up a cron job for each user?
-
How do I implement Heroku background processes?
This is a memory intensive process though and Heroku is OOM'ing with R14 errors. For this they recommend migrating intensive work like this to a Background Job via Redis, implemented in Bull and Throng
What are some alternatives?
graphql-tools - :wrench: Utility library for GraphQL to build, stitch and mock GraphQL schemas in the SDL-first approach
Bee-Queue - A simple, fast, robust job/task queue for Node.js, backed by Redis.
github-readme-streak-stats - 🔥 Stay motivated and show off your contribution streak! 🌟 Display your total contributions, current streak, and longest streak on your GitHub profile README
kue - Kue is a priority job queue backed by redis, built for node.js.
material-dashboard - Material Dashboard - Open Source Bootstrap 5 Material Design Admin
node-resque - Node.js Background jobs backed by redis.
satellite - A Microservice Framework for Telescope
agenda - Lightweight job scheduling for Node.js
novu - 🔥 The open-source notification infrastructure with fully functional embedded notification center 🚀🚀🚀
bottleneck - Job scheduler and rate limiter, supports Clustering
bedrock - Making mozilla.org awesome, one pebble at a time
better-queue - Better Queue for NodeJS