elshanakberov/hexagonal-architecture

Implementing Food ordering service using hexagonal architecture

hexagonal-architecture's Issues

Implement Sagas for data consistency

Happy path through saga is as follows

1. Order Service creates an Order in the APPROVAL_PENDING state and publishes OrderCreated event.
2. Kitchen Service consumes the OrderCreated event and creates a Ticket in a CREATE_PENDING state and publishes TicketCreated event.
3. Payment Service consumes the TicketCreated event and creates a Payment and publishes the PaymentCreated event.
4. Kitchen Service consumes the PaymentCreated event and changes the state of the Ticket to AWATING_ACCEPTANCE.
5. Order Service consumes the PaymentCreated event and changes the state of the Order to APPROVED and publishes an OrderApproved event.

Unhappy path through saga is as follows

1. Order Service creates an Order in the APPROVAL_PENDING state and publishes OrderCreated event.
2. Kitchen Service consumes the OrderCreated event and creates a Ticket in a CREATE_PENDING state and publishes TicketCreated event.
3. Payment Service consumes the TicketCreated event and creates a Payment and publishes the PaymentCreateFailed event.
4. Kitchen Service consumes the PaymentCreateFailed event and changes the state of the Ticket to REJECTED.
5. Order Service receives the PaymentCreateFailed event and changes the state of the Order to REJECTED.

Provide transactional functionality via 3rd party dependency

Remove shared common module

Implement event sourcing

Implement CI

Like Ele Like gor

Publish an event when order placed

An event store such as kafka would be great for this specific purpose.

Develop inventory service