cache VS event-dispatcher

Compare cache vs event-dispatcher and see what are their differences.

cache

Provides extended PSR-6, PSR-16 (and tags) implementations (by symfony)

event-dispatcher

Provides tools that allow your application components to communicate with each other by dispatching events and listening to them (by symfony)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
cache event-dispatcher
1 1
4,047 8,450
0.5% 0.3%
8.3 5.2
7 days ago 7 days ago
PHP PHP
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

cache

Posts with mentions or reviews of cache. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-18.
  • Decorator Pattern vs. Proxy Pattern
    2 projects | dev.to | 18 Sep 2021
    An example of a Proxy can be found in the DeflateMarshaller of the symfony/cache package. This Marshaller is restrictive due to its dependency on gzinflate() & gzdeflate() and its changes to the output of the inner instance.

event-dispatcher

Posts with mentions or reviews of event-dispatcher. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-19.
  • From a Single Repo, to Multi-Repos, to Monorepo, to Multi-Monorepo
    7 projects | news.ycombinator.com | 19 Aug 2021
    While composer does have this limitation in that packages are published by making new tags within the repo, frameworks like symfony and cakephp have workarounds where they have one monorepo where all packages are worked on, and then automation to push changes to read only repos of each component. So there's https://github.com/symfony/symfony pushing to https://github.com/symfony/event-dispatcher which gets published to packagist.

What are some alternatives?

When comparing cache and event-dispatcher you can also consider the following projects:

Doctrine Cache - Doctrine Cache component

Symfony Mailer - Helps sending emails

scrapbook - PHP cache library, with adapters for e.g. Memcached, Redis, Couchbase, APC(u), SQL and additional capabilities (e.g. transactions, stampede protection) built on top.

fjb - fast javascript bundler :package:

Laminas Cache - Caching implementation with a variety of storage options, as well as codified caching strategies for callbacks, classes, and output

amqp-messenger - Symfony AMQP extension Messenger Bridge

http-foundation - Defines an object-oriented layer for the HTTP specification

console - Eases the creation of beautiful and testable command line interfaces

http-kernel - Provides a structured process for converting a Request into a Response

cache-duration - A readable and fluent way to generate PHP cache time.

Jenkins - Jenkins automation server