php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone

KO | EN

gitlite — search

#javascript #hacktoberfest #llm #rust #linux #nodejs #java #windows #awesome #cli #kubernetes #awesome-list #pytorch #openai

php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone

(★ 110)

Ecotone - ES DDD CQRS PHP Symfony Laravel example

php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Ecotone Framework Demo Application

# Objectives

- To provide a simple example of how to implement `Domain Driven Design` and `Messaging Architecture` in PHP.  
- To show how to implement `CQRS`, `Event Sourcing` and `Hexagonal Architecture` in PHP.
- To show how to implement `Resilient`amd `Observable` `Microservices` in PHP.

# Playing with the demo

Run `docker-compose build --pull && docker-compose up -d` to start all services, and wait for them to start `docker-compose logs -f`.

This Demo provides two integrated Applications.

- Customer Service - which allows for reporting issues by customers
- Backoffice Service - which allows for working on tickets by employees

Services communicate with each other using `RabbitMQ` with `Ecotone's Distributed Bus`.

### If you do have problems running example, possibly you may need to fix file permissions

> sudo chown -R YOUR_GROUP:YOUR_USER .

### Quickstart

- To report issue as a customer, go to [Customer Service](http://localhost:3000/)    
- From [Backoffice Service](http://localhost:3001/prepared-tickets) you may start working on ticket, that was correlated with issue reported by customer.  
- You may also check [Jaeger](http://localhost:3007/) to get full overview of how communication looks like and how each component behave and what is happening.

Additionaly you may check:

- Whenever issue is reported, confirming email will be sent to the customer, which can be found [Mailbox](http://localhost:3004/).
- First time email is sent it's set up for failing, so you can get feeling of working with system that can recover from error messages using [Ecotone Pulse](http://localhost:3006/service/customer_service).

# Stack

- [Ecotone](https://docs.ecotone.tech/) - PHP Framework for building resilient, business oriented system in PHP
- [Symfony](https://symfony.com/) - PHP Framework for building web applications
- [Laravel](https://laravel.com/) - PHP Framework for building web applications
- [RabbitMQ](https://www.rabbitmq.com/) - Message Broker for asynchronous communication
- [Ecotone Pulse](https://docs.ecotone.tech/modules/ecotone-pulse) - Monitor for any processing errors and recover from failed messages.
- [OpenTelemetry with Jaeger](https://www.jaegertracing.io/) - Distributed Tracing for monitoring and troubleshooting microservices-based distributed systems

# Business Domain

## Customer Service

- `Customer Service` is `Laravel+Ecotone application`, where customers can report issues. This happens using `CQRS` combined with `Eloquent Models`.

![Laravel CQRS](https://raw.githubusercontent.com/ecotoneframework/php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone/master/documentation/customer-service.png "Laravel CQRS")

------

- Whenever new issue is reported, email is send to the with confirmation. This happens using `Asynchronous Event Handlers`, which are backed by `RabbitMQ`.

![Laravel asynchronous event handling](https://raw.githubusercontent.com/ecotoneframework/php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone/master/documentation/issue-reported.png "Laravel asynchronous events")

## Backoffice Service

- `Backoffice Service` is `Symfony+Ecotone application`, where employees can be registered and work on the tickets.  
All issues reported by customers are synchronized to `Backoffice Service` and are correlated with tickets.  
The synchronization between `Customer Service` and `Backoffice Service` is done using `Events` and `Distributed Bus` for cross service communication via `RabbitMQ`.

![Symfony Microservice](https://raw.githubusercontent.com/ecotoneframework/php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone/master/documentation/ddd-cqrs-event-sourcing-php-hexagonal-architecture.png "Symfony Microservice")

------

- Employees can work on the tickets provides information about the status. As we want to know full history, Tickets are `Event-Sourced`.    
From Event Sourced tickets we build different `Read Model Projections`, which are used to display information about the ticket.

## Tracing and Monitoring

- The whole communication between Services is monitored and traced using [OpenTelemetry](https://opentelemetry.io/) with `Jaeger`.    
![OpenTelemetry Jaeger](https://raw.githubusercontent.com/ecotoneframework/php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone/master/documentation/tracing_jaeger_php.png "OpenTelemetry Tracing in PHP with Jaeger")

------

- Any issue that happens in the system is reported to `Ecotone Pulse`, which is used to recover from failed messages.  
![Ecotone Pulse](https://raw.githubusercontent.com/ecotoneframework/php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone/master/documentation/ecotone_pulse.png "Ecotone Pulse")

php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone

php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone

php-ddd-cqrs-event-sourcing-symfony-laravel-ecotone 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README