lendo-stp-gdansk / lendo-infrastructure-bundle
Infrastructure bundle for Lendo projects usage
Package info
github.com/LendoSTPGdansk/lendo-infrastructure-bundle
Type:symfony-bundle
pkg:composer/lendo-stp-gdansk/lendo-infrastructure-bundle
Requires
- php: >=7.1
- firebase/php-jwt: ^5.0
- guzzlehttp/guzzle: ^6.2
- lendo-stp-gdansk/lendo-core-domain: <1.0.0
- ramsey/uuid: ^3.6
- symfony/framework-bundle: ~3.1|~3.3
Requires (Dev)
- atoum/atoum: ^3.0
- doctrine/annotations: ^1.4
- everzet/persisted-objects: ^1.0
- incenteev/composer-parameter-handler: ~2.1
- m6web/cassandra-bundle: ^2.1
- phing/phing: ^2.16
- php-amqplib/rabbitmq-bundle: ^1.12
- phpmd/phpmd: ^2.6
- phpspec/phpspec: dev-master
- phpunit/phpunit: ^6.1
- sebastian/exporter: ^3.1
- sebastian/phpcpd: ^3.0
- squizlabs/php_codesniffer: ^3.0
- ulff/elasticsearch-php-client-bundle: ^2.0
This package is not auto-updated.
Last update: 2017-08-30 11:26:34 UTC
README
Common bundle with implementations for specific infrastructure, used by lendo services
Storages
Event storage
Cassandra
m6web/cassandra-bundle:dev-master
Tested on: 2.2 and 3.10
Projection storage
Elasticsearch
ulff/elasticsearch-php-client-bundle:1.0
Tested on: 2.2 - 2.4
ulff/elasticsearch-php-client-bundle:2.0
Tested on: 5.0+
Queue messages
RabbitMQ
- php-amqplib/rabbitmq-bundle:1.11
- Lendo\InfrastructureBundle\RabbitMQ\BaseProducer is taking advantage of delayed-message-exchange plugin (x-delay header set up). It is configurable in config.yml:
lendo_infrastructure: rabbit_config: dead_letter_delay: xx
Default value is 30 seconds and it is available as parameter lendo_infrastructure.rabbit.dead_letter_delay.
- to enable logging for producer set:
lendo_infrastructure: rabbit_config: producers: producer-name: enable_logger: true
Tested on: 3.6.9
InMemory
External resources
To provide external resources configuration add to your service in config.yml
lendo_infrastructure: external_resources: - service: "service_name" url: "%service_url%" path: "/path/{id}" headers: Accept: application/vnd.lendo.service_name+json
Configuration will be available as a parameter resource.service_name.