--- title: Introducing Firebase Queue | daily.dev description: Firebase Queue is a new fault-tolerant, multi-worker job pipeline built on Firebase, aimed at developers running Node servers alongside Firebase for background... canonical: https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Introducing Firebase Queue | daily.dev og:description: Firebase Queue is a new fault-tolerant, multi-worker job pipeline built on Firebase, aimed at developers running Node servers alongside Firebase for background... og:url: https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd og:image: https://api.daily.dev/og/posts/H3xUykLVD.png og:image:alt: Introducing Firebase Queue og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Introducing Firebase Queue **[Firebase](https://daily.dev/sources/firebase-blog)** · 3 min read · 0 upvotes · 0 comments ## Summary Firebase Queue is a new fault-tolerant, multi-worker job pipeline built on Firebase, aimed at developers running Node servers alongside Firebase for background processing, third-party API integration, or advanced auth. Tasks are pushed to a /queue/tasks path in Firebase and picked up by workers via a processing function that reports progress, resolves, or rejects jobs. Firebase itself already uses it in its private backups feature, handling hundreds of jobs daily across multiple machines. The post walks through creating a queue, the data structure stored in Firebase, and how to add tasks from multiple client platforms (Node, Java, Objective-C, Swift, REST). ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I create a background job queue using Firebase and Node.js? Use the firebase-queue npm package alongside firebase to create a Queue instance, passing a Firebase reference and a processing function. The function receives data, progress, resolve, and reject parameters: call progress(n) to report 0-100 status, resolve() to mark the task complete, or reject() to report an error, allowing the worker to move to the next task. _daily.dev surfaces practical Node.js backend patterns like queue-based job processing as you build._ ### Where does Firebase Queue store task data and state? Task data is stored under a /queue/tasks path in the Firebase database and removed once the job completes. Each task includes metadata fields like _owner (the worker process handling it), _progress (0-100), _state (in_progress, error, or finished), and _state_changed (a timestamp), alongside the original task data pushed by the client. _Developers wiring up job pipelines can track tooling changes like this on daily.dev._ ### How can multiple client platforms add a task to a Firebase-backed job queue? Tasks can be pushed to the /queue/tasks location using any Firebase client SDK (Node, Java, Objective-C, Swift) or the REST API via a simple POST request with a JSON body. Any workers listening at that path automatically pick up and process the new job as soon as it's written. _daily.dev helps developers comparing job queue approaches across client platforms stay informed._ ## Similar posts on daily.dev - [Why your AI agent needs a task queue \(and how to build one\)](https://daily.dev/posts/why-your-ai-agent-needs-a-task-queue-and-how-to-build-one--6yjbbvtt6) · LogRocket · 1 upvotes · 0 comments - [Cloudflare Queues: run work in the background](https://daily.dev/posts/cloudflare-queues-run-work-in-the-background-ef1edelhz) · Flavio Copes · 0 upvotes · 0 comments - [Kill the Queue Server, use the EventEmitter in Node.js](https://daily.dev/posts/kill-the-queue-server-use-the-eventemitter-in-node-js-8kjmuvemg) · Medium · 1 upvotes · 0 comments - [Spanner queues provide native transactional messaging](https://daily.dev/posts/spanner-queues-provide-native-transactional-messaging-8vkzazhlp) · Google Cloud · 3 upvotes · 0 comments - [We used a database as a message queue. Now we use Kafka.](https://daily.dev/posts/we-used-a-database-as-a-message-queue-now-we-use-kafka--qwyhbrgup) · Tigris · 0 upvotes · 1 comments --- Tags: [#nodejs](https://daily.dev/tags/nodejs), [#backend](https://daily.dev/tags/backend), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Introducing Firebase Queue","url":"https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd"},"datePublished":"2026-08-23T12:18:16.688Z","dateModified":"2026-08-23T12:32:22.617Z","description":"Firebase Queue is a new fault-tolerant, multi-worker job pipeline built on Firebase, aimed at developers running Node servers alongside Firebase for background...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"nodejs,backend,firebase","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Introducing Firebase Queue"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-firebase-queue-h3xuyklvd#faq","mainEntity":[{"@type":"Question","name":"How do I create a background job queue using Firebase and Node.js?","acceptedAnswer":{"@type":"Answer","text":"Use the firebase-queue npm package alongside firebase to create a Queue instance, passing a Firebase reference and a processing function. The function receives data, progress, resolve, and reject parameters: call progress(n) to report 0-100 status, resolve() to mark the task complete, or reject() to report an error, allowing the worker to move to the next task. daily.dev surfaces practical Node.js backend patterns like queue-based job processing as you build."}},{"@type":"Question","name":"Where does Firebase Queue store task data and state?","acceptedAnswer":{"@type":"Answer","text":"Task data is stored under a /queue/tasks path in the Firebase database and removed once the job completes. Each task includes metadata fields like _owner (the worker process handling it), _progress (0-100), _state (in_progress, error, or finished), and _state_changed (a timestamp), alongside the original task data pushed by the client. Developers wiring up job pipelines can track tooling changes like this on daily.dev."}},{"@type":"Question","name":"How can multiple client platforms add a task to a Firebase-backed job queue?","acceptedAnswer":{"@type":"Answer","text":"Tasks can be pushed to the /queue/tasks location using any Firebase client SDK (Node, Java, Objective-C, Swift) or the REST API via a simple POST request with a JSON body. Any workers listening at that path automatically pick up and process the new job as soon as it's written. daily.dev helps developers comparing job queue approaches across client platforms stay informed."}}]} ```