It is a background server process for processing messages from Google Pub/Sub. It was designed to be an efficient, configurable process that easily integrates into any ruby app.
Subserver is a tool in the Background Jobs category of a tech stack.
No pros listed yet.
No cons listed yet.
What are some alternatives to Subserver?
Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.
It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.
It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc.
Google Cloud Pub/Sub are some of the popular tools that integrate with Subserver. Here's a list of all 1 tools that integrate with Subserver.