Application to demonstrate Domain Driven Design Context Mapping patterns based on variosu Spring Boot applications. Please bear in mind that the application itself is kept simplistic, in order to isolate the focus on the Context Mapping Patterns. This is the reason why you will find some logic in Controllers that should be placed in other classes in a real-world application or the reason why I use database IDs for a general purpose.
Also keep in mind that some of the Context Mapping Patterns not best practices but are things that are found in existing, historically grown applications. Context Mapping is mostly a way to look at existing solutions and this code example is an existing solution that has some intentionally built in issues.
A good starting point for your analysis is the CreditApplicationController in credit-application as it implements the main workflow.
- You need a current version of Maven
- A basic installation of Redis must be installed and running (redis-server)
There is no "one-stop" build and install script as of yet so you will have to take a few easy manual steps that you should run in this specific order:
- Start your redis-server
- Build the scoring-shared-kernel module
- Build the customer application
- Run the customer application
- Run mvn jaxb2:generate in credit-application while the customer application is running
- Run the scoring application
- Run the credit-agency application
- Run the customer-contact application
- Run the credit-application application
- Start entering data at http://localhost:9090
Each of the modules is it's own Spring Boot Application which can be accessed as follows:
| Name | Application / Enpoint Type | Port | URL |
|---|---|---|---|
| Credit Application | Web App | 9090 | http://localhost:9090/ |
| Customer | WSDL Endpoint | 9091 | http://localhost:9091/ws/ or http://localhost:9091/ws/customer.wsdl for the wsdl |
| Credit Agency | REST Endpoint | 9092 | http://localhost:9092/personRating |
| Scoring | RMI Endpoint | 1199 | http://localhost:1199/scoringService |
| Customer Contact | No active server endpoint, listens to Redis on the following topics: customer-created-events, credit-application-approved-events | No open port | No available URL for access |