# Never ever use a database as a message queue. Do this instead.

DevFeed: [Never ever use a database as a message queue. Do this instead.](<https://devfeed.tech/articles/never-ever-use-a-database-as-a-message-queue-do-this-instead-6011.md>)

Original publisher: [Read original article](<https://turso.tech/blog/never-ever-use-a-database-as-a-message-queue-do-this-instead-f99c188b>)

Author: Glauber Costa

Published: 2022-08-23T00:00:00Z

Content type: article

Language: en

Sources: [Turso Blog](<https://devfeed.tech/sources/turso-blog.md>)

Topics: [Turso](<https://devfeed.tech/topics/turso.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [libSQL](<https://devfeed.tech/topics/libsql.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [database](<https://devfeed.tech/tags/database.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [libsql](<https://devfeed.tech/tags/libsql.md>), [message-queue](<https://devfeed.tech/tags/message-queue.md>), [queue](<https://devfeed.tech/tags/queue.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [turso](<https://devfeed.tech/tags/turso.md>)

## AI overview

The article argues against using a database as a message queue and proposes an alternative. The supplied text describes Turso as a backend and data-layer platform built from a rewrite of SQLite, with database access over the wire and synchronization to devices and servers. It also notes that the post references an older version of Turso.

## Source excerpt

If you are an application developer and need a full backend, including the data layer, you have two choices: Relying on a backend team may be the solution we all want. But often, especially with...