Need advice about which tool to choose?Ask the StackShare community!

Hangfire

143
222
+ 1
17
PHP-FPM

103
112
+ 1
0
Add tool

Hangfire vs PHP-FPM: What are the differences?

Hangfire: Perform background processing in .NET and .NET Core applications. 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; PHP-FPM: * An alternative FastCGI daemon for PHP*. 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.

Hangfire and PHP-FPM can be primarily classified as "Background Processing" tools.

Hangfire is an open source tool with 4.93K GitHub stars and 1.12K GitHub forks. Here's a link to Hangfire's open source repository on GitHub.

Gbase, TrackJS, and PagueVeloz are some of the popular companies that use Hangfire, whereas PHP-FPM is used by nefisyemektarifleri.com, OTTLabs, and ARENA. Hangfire has a broader approval, being mentioned in 9 company stacks & 9 developers stacks; compared to PHP-FPM, which is listed in 9 company stacks and 8 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Hangfire
Pros of PHP-FPM
  • 7
    Integrated UI dashboard
  • 5
    Simple
  • 3
    Robust
  • 2
    In Memory
  • 0
    Simole
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    No Stats
    - No public GitHub repository available -

    What is Hangfire?

    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.

    What is PHP-FPM?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Hangfire and PHP-FPM as a desired skillset
    CBRE
    Mexico Ciudad de Mexico Mexico City
    CBRE
    United Kingdom of Great Britain and Northern Ireland England Feltham
    What companies use Hangfire?
    What companies use PHP-FPM?
    See which teams inside your own company are using Hangfire or PHP-FPM.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Hangfire?
    What tools integrate with PHP-FPM?
      No integrations found
      What are some alternatives to Hangfire and PHP-FPM?
      RabbitMQ
      RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
      NServiceBus
      Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.
      Azure Functions
      Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.
      Kafka
      Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
      Sidekiq
      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.
      See all alternatives