Ceph Reviews

Resque Reviews

Ceph mentions (11)

• 10 open source tools that platform, SRE and DevOps engineers should consider in 2024.

  Ceph stands out in storage technology, offering a scalable and reliable solution where traditional systems fall short. It supports object, block, and file storage in one system, adaptable for various environments including on-premises, cloud, or container-native setups. Key benefits include scalability, enabled by the CRUSH algorithm, allowing for expansion without typical downtime. This makes Ceph suitable for... - Source: dev.to / 5 months ago

• iSCSI over WAN / backup of remote site

  With that being said, you better take a look at something more WAN optimized and more secure, like S3 storage. You can build the S3 storage (and gain immutability) using something like MinIO (https://min.io/) or Ceph (https://ceph.io/en/) or check out Object First Ootbi offerings - https://objectfirst.com/object-storage/ (I work for them). Source: 10 months ago

• What's the best AWS S3 protocol alternative?

  I believe Ceph [1] could be a good alternative. It can be self hosted and I believe some cloud providers also offer it. Here are some differences between S3 and Ceph [2]. [1] - https://ceph.io/en/ [2] - https://www.lightbitslabs.com/blog/ceph-storage/. - Source: Hacker News / 12 months ago

• Seeking Advice & Opinions: Hybrid NAS/Cloud Storage for Family Use

  Another option is a distributed Ceph cluster https://ceph.io/en/. Source: over 1 year ago

• First Time NAS buyer for Digital Textile Printing Factory

  There's also cool systems like https://ceph.io/en/ that could be efficient if willing to set up and learn. Source: almost 2 years ago

Resque mentions (5)

• Add web scraping data into the database at regular intervals [ruby & ror]

  You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically. Source: almost 2 years ago

• How to run a really long task from a Rails web request

  So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago

• Building a dynamic staging platform

  Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck. - Source: dev.to / about 2 years ago

• #30DaysofAppwrite : Appwrite’s building blocks

  The Schedules worker corresponds to the appwrite-schedule service in the docker-compose file. The Schedules worker uses a Resque Scheduler under the hood and handles the scheduling of CRON jobs across Appwrite. This includes CRON jobs from the Tasks API, Webhooks API, and the functions API. - Source: dev.to / about 3 years ago

• A quick look at background jobs in Ruby

  There are a few of popular systems. A few need a database, such as Delayed::Job, while others prefer Redis, such as Resque and Sidekiq. - Source: dev.to / about 3 years ago