I think the api endpoint that loads it up into the db is how it’s intended to work. Data transfer solutions are frequently used to move data from point A to points B, C, and D without requiring a lot of effort on A’s part.

Whether the queue pushes to the api, or if it gets polled, is another conversation.

“Native” solutions basically do exactly this. When you make a replica of MySQL, it’s based off the binlog (a queue). This binlog can also be used to make replicas of other types of dbs.

In addition, you could try to have timescaledb be the persistent store rabbitmq backs up to. A backup is also the equivalent of a replica, but just doesn’t get read from. It’s probably not recommended to backup rabbitmq into timescaledb’s format because of data compression and how the keys work.

Hence, your best option would be to just make an api, receive a message or poll from the queue, and send it to timescaledb.