Implementing the Domain Services (Hexagonal Architecture with Spring Boot — Part 3)

This is the third article of a 4 5 part series explaining Hexagonal Architecture and how to implement such an architecture using Spring Boot and TDD.

Part 2 of the video is live now:

Domain Services

At the end of implementing the REST API adaptor, we have mocked out two domain services GetStockPositionService and GetStockMarketValueService.

As you go through the code below, notice that we will write the domain services functionally, and we can test them without using the Spring framework for dependency injection. Testing domain services functionally and without the Spring framework enables very fast testing.

Also, notice that where the domain services need to call some adaptors, whether data repository or external services, a port to interface is used. Again, in the tests, we specify the required behaviour of these adaptors through these ports, and the domain services does not have to know any further details of these adaptors beyond their behaviours.

Let’s start with the test for GetStockPositionService, GetStockPositionServiceTest as shown here:

package com.example.hexademo.domain.service; // imports not shown class GetStockPositionServiceTest { private final StockPositionsRepository repository = mock(StockPositionsRepository.class); private final GetStockPositionService subject = new GetStockPositionService(repository); @Test void get() { // arrange String user = DomainModelFaker.fakeUser(); String symbol = DomainModelFaker.fakeStockSymbol(); StockPosition fakeStockPosition = DomainModelFaker.fakeStockPosition(user, symbol); when(repository.findOneByUserAndSymbol(user, symbol)).thenReturn(Mono.just(fakeStockPosition)); // act Mono<StockPosition> result = subject.get(user, symbol); // assert StepVerifier.create(result) .expectNext(fakeStockPosition) .verifyComplete(); } }