mvf-tech / servicer
Defines common php consumers
Requires
- php: ^7.4|^8.0
- ext-redis: *
- drupsys/servicer-contracts: ^1.0
- guzzlehttp/guzzle: ^7.4
- lstrojny/functional-php: ^1.17
- nesbot/carbon: ^2.58
- psr/container: ^1.0|^2.0
Requires (Dev)
- symfony/var-dumper: ^4.2
- dev-master
- 1.3.3
- 1.3.2
- 1.3.1
- 1.3.0
- 1.2.0
- 1.1.0
- 1.0.7
- 1.0.6
- 1.0.5
- 1.0.4
- 1.0.3
- 1.0.2
- 1.0.1
- 1.0.0
- 0.13.5
- 0.13.4
- 0.13.3
- 0.13.2
- 0.13.1
- 0.13.0
- 0.12.1
- 0.12.0
- 0.11.1
- 0.11.0
- 0.10.2
- 0.10.1
- 0.10.0
- 0.9.0
- 0.8.3
- 0.8.2
- 0.8.1
- 0.8.0
- 0.7.15
- 0.7.14
- 0.7.13
- 0.7.12
- 0.7.11
- 0.7.10
- 0.7.9
- 0.7.8
- 0.7.7
- 0.7.6
- 0.7.5
- 0.7.4
- 0.7.3
- 0.7.2
- 0.7.1
- 0.7.0
- 0.6.2
- 0.6.1
- 0.6.0
- 0.5.3
- 0.5.2
- 0.5.1
- 0.5.0
- 0.4.4
- 0.4.3
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.2
- 0.3.1
- 0.3.0
- 0.2.0
- 0.1.0
- 0.0.3
- 0.0.2
- 0.0.1
- dev-AB-2378
- dev-MER-1489
- dev-fix_tags
- dev-revert_MER-1351
- dev-MER-1168
- dev-MER-1151
- dev-MER-1095
- dev-MER-1054
- dev-MER-990
- dev-MER-948
This package is auto-updated.
Last update: 2024-03-21 09:59:12 UTC
README
Various helpers that can be used in PHP to simplify event creation and consumption.
This package is meant to be used together with event-consumer re-usable service.
Getting started
In this section you will see how to set up a PHP application to consume and publish events.
Ingress (Event Consumer)
In order to consume events in a PHP application you will need to use event-consumer re-usable service. This service is a node based application which is needed due to the limitations of PHP, long story short, php is not great for long-running tasks, when a PHP process runs for a long time without any restarts there tends to be resource leaks and various other issues that make PHP based consumers unreliable.
In the diagram above you can see what this architecture looks like. The event-consumer service reads messages (events) stored in the SQS queues and sends each consumed message to the events endpoint on your webserver.
Posting event messages over network in this way is a bit strange but this allows us to achieve 2 things that are normally really hard in PHP.
This puts a webserver (either apache or nginx) in between the
event-consumerand ourEventHandler, this is the easiest and the most reliable way to achieve "concurrency" in PHP. NOTE There are alternatives approaches e.g.ReactPHP, however, they are not commonly used in the PHP community.This avoids long-running processes, each message is handled by a different instance of a PHP process avoiding various issues long-running processes have in PHP.
In your application you will need two things:
Controllerwhere theeventsroute will be handlesPsr\Container\ContainerInterfacecompatible container, this is where you will register any dependencies required by the controller and yourEventHandlers
Learn how to set up: