Skip to content

Latest commit

 

History

History
145 lines (121 loc) · 5.57 KB

README.md

File metadata and controls

145 lines (121 loc) · 5.57 KB
Raw

CQRS hands-on

Background

  • User actions create different kind of events within the system and collected by the "event-publisher" service
    • Main objective of the "event-publisher" is to validate the event-data and store it (currently mongoDB database)
  • Events are aggregated into different views/snapshots within the "projection-aggregator" service to be displayed in the web-ui
    • We refer to this as the 'fastlane,' which we use for views or snapshots driven by user feedback—where near real-time product updates are expected by the user
    • Aggregation can be triggered on-demand or via a background process/task (in this example only on-demand is implemented)
  • General business use-case:
    • Every user is identified by a "userId" and is part of a group/school-class identified by a "groupId"
    • Users are categorized as either teachers or students (with the focus in this example on events related to students).
    • A teacher acts a maintainer for a group/class, i.e. a teacher can add or remove students from a group. This will create "AddStudentEvent" resp. "RemoveStudentEvent" per student.
    • A teacher can assign an exercise (identified by an "exerciseId", which refers to a static-content file) to students within a group/class (e.g. homework). This will create an "AssignmentEvent" per student. To distinguish between assignments the event contains an additional "assignmentId".
    • Students will work on assigned exercises which eventually creates an "ExerciseFinishedEvent" per student and assignment. The "ExerciseFinishedEvent" contains the number of errors made ("numErrors") and the maximum number of errors of the exercise, i.e. "numErrors == 0" is the perfect score and "numErrors == maxErrors" the worst possible score.
    • Based on performance the teacher will award students with coins (i.e. good job) and stars (i.e. exemplary job), which creates an "AwardCoinsAndStarsEvent" per student.

Local development

Requirements

  • JDK == 17
  • docker/docker-compose are optional if a mongodb is available by some other means
  • curl or some alternative means to execute http requests
  • Suggested IDE: IntelliJ with ktlint plugin

Frameworks used

  • Build tool: gradle
  • Formatting/linting: ktlint
  • Http/Rest framework: ktor
  • Dependency injection: koin
  • Functional helpers: Arrow

Common commands

  • Start a local mongodb (if not available otherwise)

    docker-compose up -d --wait

  • Clean and build everything

    ./gradlew clean
./gradlew build

  • Reformat code

    ./gradlew ktlintFormat

  • Start event-publisher in dev-mode (on port 8123)

    ./gradlew :event-publisher:run

  • Start projection-aggregator in dev-mode (on port 8124)

    ./gradlew :projection-aggregator:run

  • Reset/empty the test-database:

    docker exec -ti cqrs-handson-mongo_db-1 mongosh --eval 'use backend; db.dropDatabase()'

Fixture

  • Add the event fixtures to a running event-publisher 
    curl -X POST -d @common/src/testFixtures/resources/fixtures/events.json -H "Content-Type: application/json"  http://localhost:8123/v1/publish
  • Simulated behaviour:
    • Teacher adds students "100, 101, 102, 103, 104" to group/class "1000" and students "200, 201, 202" to group/class "2000"
    • Correcting a mistake student "104" is removed from group/class "1000"
    • Teacher hands out an assignment of exercise "https://content.demo.nowhere/someexercise" to all students in group "1000"
    • Teacher hands out an assignment of exercise "https://content.demo.nowhere/someotherexercise" to all students in group "2000"
    • All students except "101" and "201" complete the assignment with different success
    • Teacher awards coins and stars to all students that have completed the assignment
  • Students are then able to query their coins and stars from the projection-aggregator service: 
    curl http://localhost:8124/v1/projections/coins_and_stars/user/$USER_ID
    e.g. 
    > curl http://localhost:8124/v1/projections/coins_and_stars/user/100
{"coins":3,"stars":1}
  • The teacher is able to query the current members of each group/class: 
    curl http://localhost:8124/v1/projections/group_members/group/$GROUP_ID
    e.g. 
    > curl http://localhost:8124/v1/projections/group_members/group/1000
{"members":[100,101,102,103]}

Programming exercise

Add an "assignment_results" aggregator for the teacher for an overview off all results of all assignments handed out to a group/class.

  • Example result might look like: 
    > curl http://localhost:8124/v1/projections/assignment_results/group/1000
{
  "assignments": [{
    "assignmentId": 9000,
    "results": [{
      "userId": 100,
      "numErrors": 0,
      "maxErrors": 10
    }, {
      "userId": 102,
      "numErrors": 3,
      "maxErrors": 10
    }, {
      "userId": 103,
      "numErrors": 5,
      "maxErrors": 10
    }]
  }]
}
  • Using maps instead of lists would work as well
  • Added bonus would be a list of all students that have not completed their assignment (yet?)

Quiz

  • What can be optimized?
  • What needs to be refactored and/or added to be ready for production?

Open discussion

  • How can the projection-aggregator be extended so that aggregates/snapshots are updated in the background rather than on demand?
  • How can coins and stars be awarded to the students automatically based on error percentage in the assignment results?