Dave Copeland :ruby: on Nostr: Other change is to caution adoption of Solid Queue, especially if you are ...
Other change is to caution adoption of Solid Queue, especially if you are successfully operating Sidekiq. Solid Queue is untested for MANY use-cases and doesn't provide any feature you can't already find in more mature offerings. But, it's part of Rails so worth watching.
Published at
2025-01-09 02:30:49Event JSON
{
"id": "ac19e1f460cc8a9367d5be47bf36cd39bedd084ea0eac2ceca730717940d57fc",
"pubkey": "0a98fcc74400896d68beecfb32da230c656db6fc7ab43c4228b7755377d294f2",
"created_at": 1736389849,
"kind": 1,
"tags": [
[
"e",
"bff894c054d26fa98f07d10ae07ebca6d8ad27d75ba46d6e058ecf2e69e57a72",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://ruby.social/users/davetron5000/statuses/113796045149900805",
"activitypub"
]
],
"content": "Other change is to caution adoption of Solid Queue, especially if you are successfully operating Sidekiq. Solid Queue is untested for MANY use-cases and doesn't provide any feature you can't already find in more mature offerings. But, it's part of Rails so worth watching.",
"sig": "6b05824c4e314fdc63c6628b0bf7512a53480e8cb177fe992bc3b7c90f8eb1f4c6f42140e95c1ea35ea795a9cabb963b15677d2939126c0d66c588af329da998"
}
