Sample code for the Pluralsight DDD Fundamentals course (coming soon) by Julie Lerman and Steve "ardalis" Smith. If you are looking for the .NET Framework sample from the original 2014 DDD Fundamentals course, it's available as the ddd-vet-clinic sample.

If you like or are using this project to learn, please give it a star. Thanks!

1. Running the Sample

  1.1 Docker

  1.2 Visual Studio

2. Student Recommendations

3. Architecture Notes

4. Developer Notes

5. Credits

You can run this sample in Docker or in Visual Studio. Docker is recommended.

The easiest way to run the sample is using docker. Download the source and run this command from the root folder:

docker-compose build --parallel
docker-compose up

The build step will take a while. It's way faster if you run it in parallel, assuming you have a fast machine and download speed. The up command is much faster but will also take a moment and you may see some errors as apps try to connect to docker or databases before they're responsive. Give it a minute or two and it should succeed. RabbitMQ errors should go away once that service starts up. If you get SQL Server login errors, I've found it's best to just restart everything (ctrl-c, then docker-compose up again).

This will start RabbitMQ (for messaging between apps) and build and run each of the applications involved in the sample:

• FrontDesk.Api
• FrontDesk.Blazor
• ClinicManagement.Api
• ClinicManagement.Blazor
• VetClinicPublic

It also adds the following supporting containers:

• RabbitMQ with Management
• FrontDesk SQL Server
• ClinicManagement SQL Server
• Test Mailserver (Papercut)

Once running, you should be able to access the various apps using localhost (HTTP not HTTPS because of Kestrel configuration restrictions) and the following ports (you can also find these bindings in the docker-compose.yml file):

The ports in () are only open inside of docker, not exposed otherwise.

Here are the (localhost) links you should use once the apps are running in docker:

• FrontDesk
• Clinic Management
• VetClinicPublic (there are links here to send test emails and view them, too)

If you want to quickly clean up all of your docker containers (All of them not just the ones you created for this sample!) you can run this command:

docker kill $(docker ps -q)

Note that any data changes you make will not be persisted if you docker remove the SQL Server container. The Docker container for SQL Server will be recreated and seeded on the next docker run. In other scenarios, you might be using Docker volumes to persist or share the database across container instances but that's overkill for this demo.

Running the sample from Visual Studio requires some additional setup. You will need to run multiple solutions side by side. You will also need to run RabbitMQ, ideally as a docker image, which you can so using this command:

docker run --rm -it --hostname ddd-sample-rabbit -p 15672:15672 -p 5672:5672 rabbitmq:3-management

You should be able to open localhost:15672 to view RabbitMQ management interface (login as guest/guest).

When new appointments are created, confirmation emails are sent out to clients. Start a test mailserver using this command (learn more):

docker run --name=papercut -p 25:25 -p 37408:37408 jijiechen/papercut:latest

You should be able to open localhost:37408 to view Papercut test mailserver management interface, where sent emails will appear.

You can run individual solutions independently from one another, but obviously you won't see live sync between them when entities are updated, new appointments created, appointment confirmation emails clicked, etc. To get that, you'll need to run all three of the web applications:

• FrontDesk
• ClinicManagement
• VetClinicPublic

Some of the ports may not be set up in config; you may need to adjust them by hand. They assume you'll run primarily in docker to see everything running. If you're trying to get things working outside of docker, you should try with the ports shown in the table above.

If you're coming here from the Pluralsight Domain-Driven Design Fundamentals course, great! Download this sample and look around. See if you can run it on your machine (docker recommended). Your next assignment is to look at the TODO comments in the code, and see if you can implement any of them. You can view todo comments as tasks in Visual Studio, or there are plugins for VS Code.

Don't worry about submitting a pull request for any TODO comments you fix. They're left there intentionally to help students learn by providing some ways to extend the solution from the course.

This sample is from Julie Lerman and Steve Smith's Pluralsight course. The original sample was written for .NET Framework by Steve. The current .NET 5 version was initially ported with the help of Shady Nagy. Progress Software provided the Blazor Scheduler control used to display the clinic's schedule. Additional credits include:

• Your name could be here...