home.social

#solidqueue — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #solidqueue, aggregated by home.social.

fetched live
  1. 🎉 Wow, Solid Queue 1.6.0 finally supports fiber workers! 🚀 Because, you know, the world was really struggling without super-fast, async, fiber execution modes in their **queues**. Surely, this groundbreaking change will save humanity from its impending doom — or at least from slightly slower queue processing. 🤷‍♂️
    github.com/rails/solid_queue/r #SolidQueue #FiberSupport #AsyncExecution #TechUpdate #QueueProcessing #HackerNews #ngated

  2. 🎉 Wow, Solid Queue 1.6.0 finally supports fiber workers! 🚀 Because, you know, the world was really struggling without super-fast, async, fiber execution modes in their **queues**. Surely, this groundbreaking change will save humanity from its impending doom — or at least from slightly slower queue processing. 🤷‍♂️
    github.com/rails/solid_queue/r #SolidQueue #FiberSupport #AsyncExecution #TechUpdate #QueueProcessing #HackerNews #ngated

  3. 📊 Built on #Prometheus metrics, #AlertManager notifications & #OpenTelemetry tracing for complete observability

    🗄️ Uses #SQLite for storage & #SolidQueue for background jobs - lightweight #Rails engine architecture

    🔐 HTTP probes every 30s, SMTP checks with STARTTLS/SSL verification & MTR-based traceroute monitoring

    🎨 Dashboard with dark/light mode, uptime history & probe status visualization across all sites

  4. 📊 Built on #Prometheus metrics, #AlertManager notifications & #OpenTelemetry tracing for complete observability

    🗄️ Uses #SQLite for storage & #SolidQueue for background jobs - lightweight #Rails engine architecture

    🔐 HTTP probes every 30s, SMTP checks with STARTTLS/SSL verification & MTR-based traceroute monitoring

    🎨 Dashboard with dark/light mode, uptime history & probe status visualization across all sites

  5. 🚀 Ah, the classic tale of unrequited love in tech: dumping #Redis for #SolidQueue, only to be ghosted by a 403 error. 😆 Can't even break up with a database without getting friend-zoned by nginx! 🔒
    simplethread.com/redis-solidqu #unrequitedlove #techfail #nginx #HackerNews #ngated

  6. 🚀 Ah, the classic tale of unrequited love in tech: dumping #Redis for #SolidQueue, only to be ghosted by a 403 error. 😆 Can't even break up with a database without getting friend-zoned by nginx! 🔒
    simplethread.com/redis-solidqu #unrequitedlove #techfail #nginx #HackerNews #ngated

  7. We'll also have the one-and-only Rosa Gutierrez, Maintainer of #SolidQueue!

  8. We'll also have the one-and-only Rosa Gutierrez, Maintainer of #SolidQueue!

  9. 🚨🚂 Welcome aboard the 🚀 #AppSignal 🛤️ express, where buzzwords like "Solid Queue" sound like a hipster brunch choice and "Anomaly Detection" is your morning coffee spilling! ☕ Who knew Ruby on Rails needed more rails and less ruby? 🤷‍♂️
    blog.appsignal.com/2025/05/07/ #SolidQueue #AnomalyDetection #RubyOnRails #TechTrends #HackerNews #ngated

  10. 🚨🚂 Welcome aboard the 🚀 #AppSignal 🛤️ express, where buzzwords like "Solid Queue" sound like a hipster brunch choice and "Anomaly Detection" is your morning coffee spilling! ☕ Who knew Ruby on Rails needed more rails and less ruby? 🤷‍♂️
    blog.appsignal.com/2025/05/07/ #SolidQueue #AnomalyDetection #RubyOnRails #TechTrends #HackerNews #ngated

  11. I'm adding background jobs to my new app (Rails7.2 + SolidQueue), and not sure how things should be designed.
    I need to run daily job to generate notifications on user-created task due/reminder date.

    Should I:

    1) create one job that iterates all relevant tasks and generates notifications? (might get slow with more users)

    2) have one job that iterates tasks, and creates separate job for every relevant task?

    3) something else?

    #rubyonrails #activejob #SolidQueue

  12. I'm adding background jobs to my new app (Rails7.2 + SolidQueue), and not sure how things should be designed.
    I need to run daily job to generate notifications on user-created task due/reminder date.

    Should I:

    1) create one job that iterates all relevant tasks and generates notifications? (might get slow with more users)

    2) have one job that iterates tasks, and creates separate job for every relevant task?

    3) something else?

    #rubyonrails #activejob #SolidQueue