Skip to content

Commit

Permalink
Updated readme
Browse files Browse the repository at this point in the history
- mention pricing_catalog app
- added ✅ to mark which goals are kind of achieved
  • Loading branch information
andrzejkrzywda committed Feb 12, 2024
1 parent c5f96c1 commit 0b5ea65
Showing 1 changed file with 16 additions and 11 deletions.
27 changes: 16 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,10 +62,15 @@ The customer perspective is "simulated" only - via using the select box.

### Read models

Read models live at the application level. In our case it's in the Rails app:
Read models are application specific so they live at the application level.
In our case it's in the main ecommerce Rails app:

[Read models](https://github.com/RailsEventStore/ecommerce/tree/master/rails_application/app/read_models)

Additionally, we have created the Pricing Catalog application that is a separate Rails application.
It's a good example of how to create a separate application that uses the same domains, but has different read models.


### Process Managers

#### Release payments when order expired
Expand Down Expand Up @@ -93,16 +98,16 @@ It does it, when a successful payment is detected.

This project has several high-level goals:

- to show that it's possible to modularize a non-trivial Rails app
- to serve as an example of a DDD project (not only in Rails)
- to let people play with this codebase to get a feel if DDD is for them
- to show that tests can be fast if the app is well modularized
- to show a proper pyramid of tests
- to teach event-driven architectures
- to show how to use RailsEventStore
- to bring DDD enthusiasts from .Net/Java/PHP/others to the Ruby world 😎
- to popularize professional testing techniques - mutation testing
- to allow programmers to reuse existing and popular domains
- to show that it's possible to modularize a non-trivial Rails app
- to serve as an example of a DDD project (not only in Rails)
- to let people play with this codebase to get a feel if DDD is for them
- to show that tests can be fast if the app is well modularized
- to show a proper pyramid of tests
- to teach event-driven architectures
- to show how to use RailsEventStore
- to bring DDD enthusiasts from .Net/Java/PHP/others to the Ruby world 😎
- to popularize professional testing techniques - mutation testing
- to allow programmers to reuse existing and popular domains (shown in `pricing_catalog` app)
- to build new apps like Lego

# Contributing guide
Expand Down

0 comments on commit 0b5ea65

Please sign in to comment.