/2019-01-22-oreilly-online-trng

2019-01-22-oreilly-online-trng created by GitHub Classroom

Primary LanguageJavaDo What The F*ck You Want To Public LicenseWTFPL

Domain-Driven Design and Event-Driven Microservices

Learning a Pathway to Evolutionary Architecture

Welcome to the Lab Environment!

You have now successfully acquired your own private copy of the lab exercises and instructions. This is your sandbox, and you can feel free to make changes, commit and push those changes, etc. You’ll also find guidance here on how to complete the labs and run the tests. Happy coding!

Warning
 While this is your repository, please don’t make changes to any of the implemented code that already has passing tests during the labs. If you break that code, you may not be able to successfully complete the labs.

Setup Guide

If you’ve gotten this far, we can safely assume that your Git/GitHub setup is correct. All that remains is to import the code into your IDE of choice and run your first tests.

Note
 While IDE choice should not matter, these instructions have only been tested in IntelliJ IDEA.

  1. Ensure your workstation has a proper Java 8 installation.

  2. You will need to make sure your IDE is properly configured for Lombok. At the following links, you can find instructions for Eclipse and IntelliJ IDEA.

  3. Import pom.xml as a Maven project into your IDE.

  4. Run com.mattstine.dddworkshop.pizzashop.suites.SetupSuite to demonstrate that all of the implemented tests are passing.

  5. Assuming you’ve gotten this far, you’re ready to submit your setup lab. Read on!

Lab Submission Guide

Now we’ll ensure that you are properly setup for submitting completed labs to GitHub and viewing your results in TravisCI.

Note
 While submission of your lab implementations is entirely optional, it will help your instructor gauge everyone’s progress, as well as provide him the opportunity to provide custom feedback in your repository!

  1. Find com.mattstine.lab.setup.HelloWorldTest. This test should currently be failing.

  2. Make it pass!

  3. Change the script property in .travis.yml to read: mvn test -B -P FirstSubmission

  4. You’ll now want to commit your changes to Git. When submitting labs, please prefix your commit with [NAME OF LAB] in order to make it easier to track down. For this lab, you’ll prefix with [SETUP]. For Lab 1, you’ll prefix with [LAB 1]. And so on…​

  5. Push your changes to GitHub.

  6. Visit http://travis-ci.com, and sign in with your GitHub account. If you are not already a Travis CI user, you will need to complete the following steps.

    travis

  7. You will be asked to authorize Travis CI to access data from your GitHub account. You will have to accept to continue. If you are not comfortable with this authorization, you will be able to complete the labs (if you’re here, I assume you’ve cloned the repo), but you won’t be able to submit for feedback.

    authorize travis

  8. You may be asked by GitHub to confirm your password.

    password

  9. Travis CI will sync any enabled repos in your GitHub account. Your class repo should already be there as well, and should have a successful build.

    travis repo

  10. Assuming you’ve gotten this far, you’re ready to start Lab 1!

Lab Guides

TODO: these need to be written

  • Lab 1 - TDD Aggregate Root - Create Kitchen Commands with Business Logic and Invariants

  • Lab 2 - TDD Aggregate Root - Create and Publish Kitchen Domain Events

  • Lab 3 - TDD Aggregate Repository - Create Kitchen Repositories and Add Domain Events

  • Lab 4 - TDD Aggregate Repository - Rehydrate Kitchen Aggregates by Reference

  • Lab 5 - TDD Policy - Subscribe to a Kitchen Domain Event from within an Aggregate and Create CQRS View

  • Lab 6 - TDD Application Service - Expose Kitchen Business Interface and Implement Transactions

  • Lab 7 - TDD Policy - Subscribe to a Kitchen Domain Event from an Adjacent Aggregate and Update State