@@ -43,7 +43,6 @@ ecommerce/
4343├── ordering
4444├── payments
4545├── pricing
46- ├── processes
4746├── product_catalog
4847├── shipping
4948└── taxes
@@ -57,7 +56,6 @@ ecommerce/
5756* [ Ordering] ( ecommerce/ordering/README.md )
5857* [ Payments] ( ecommerce/payments/README.md )
5958* [ Pricing] ( ecommerce/pricing/README.md )
60- * [ Processes] ( ecommerce/processes/README.md )
6159* [ Product Catalog] ( ecommerce/product_catalog/README.md )
6260* [ Shipping] ( ecommerce/shipping/README.md )
6361* [ Taxes] ( ecommerce/taxes/README.md )
@@ -97,25 +95,10 @@ It's a good example of how to create a separate application that uses the same d
9795
9896### Process Managers
9997
100- #### Release payments when order expired
101-
102- There's a process manager responsible for dealing with the process of
103- expiring orders.
104-
105- It takes the following events as the input:
106- - Ordering::OrderPlaced
107- - Ordering::OrderExpired
108- - Ordering::OrderConfirmed
109- - Payments::PaymentAuthorized
110- - Payments::PaymentReleased
111-
112- When certain conditions are met the process manager return a
113- ` ReleasePayment ` command.
114-
115- #### Confirm order when payment successful
98+ Processes are application specific so they live at the application level.
99+ In our case it's in the main ecommerce Rails app:
116100
117- Another process manager is responsible for confirming order.
118- It does it, when a successful payment is detected.
101+ [ Processes] ( https://github.com/RailsEventStore/ecommerce/tree/master/rails_application/app/processes )
119102
120103
121104# Contributing guide
0 commit comments