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.

You also have the choice of working on the labs within a browser-based IDE environment called Repl.it. If you would like to do this, just click on the "Work in Repl.it" button at the top of this README document. If this button is not present, it's possible that GitHub Classroom has not finished configuring your repo. Just wait a moment and refresh the browser.

When you enter the Repl.it IDE, it will look similar to below. You can click the "Run" button to execute your first tests, and you can use the Version Control icon to perform your commits. You also have a shell tab that will allow you to run basic UNIX commands.

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

1. Ensure your workstation has a proper Java 11 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 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 and viewing your results in GitHub.

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. 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...

4. Push your changes to GitHub.

5. GitHub Classroom has configured your repository to "autograde" your submissions. You can view the progress of this autograding by clicking on "Actions":

   

   followed by the commit you want to view:

   

   and then "Autograding":

   

   GitHub will grade ALL of the labs each time you submit, so don't be alarmed by the failures. For your Setup Submission, if you search the output for "Setup Lab" you should find a green checkmark.

   

6. Finally, if you click on "Pull requests":

   

   you will find a single PR entitled "Feedback":

   

   This PR will allow me to provide you with feedback on your work. For example, if you run into test failures that you do not understand, just go ahead and commit/push that code, then contact me in the private chat window within the O'Reilly Learning Platform. I can then take a look at your code and provide you with feedback on the commit.

   

7. Assuming you've gotten this far, you're ready to start Lab 1!

Lab Guides

• 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