Skip to content
Jivejdon is a Domain Driven Design appication with CQRS/ES/Clean/Hexagonal architecture
Java JavaScript CSS Other
Branch: master
Clone or download
Latest commit 379f951 Nov 7, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
application fixed bug Nov 7, 2019
ddl fix bug Dec 6, 2018
doc refactor command and domain events Oct 28, 2019
src/main fixed bug Nov 7, 2019
.gitignore refactor to Hexagonal(api and spi) Oct 24, 2019
CHANGES.TXT fixed Jun 30, 2019
Dockerfile.db add docker Dec 25, 2018
Dockerfile.web fix bug Dec 25, 2018
license.txt jivejdon is opensource now Aug 19, 2018
pom.xml fix bug Dec 21, 2018
readme.md refactor command and domain events Oct 28, 2019

readme.md

Jivejdon

Jivejdon is a full DDD application with Event Soucing/CQRS and clean architecture/Hexagonalarchitecture, powered by jdonframework ,running for over ten years in: https://www.jdon.com/forum

Use Case

avatar

DDD Aggregate Model

avatar

There are two aggregate roots in jivejdon: FormThread and ForumMessage(Root Message).

com.jdon.jivejdon.domain.model.ForumMessage is a rich model, no "public" setter method, all setter methods are "private":

avatar

Domain Model principles:

  1. High level of encapsulation

All members setter method are private by default, then internal. need heavy builder pattern to create aggregate root!

  1. High level of PI (Persistence Ignorance)

No dependencies to infrastructure, databases, other stuff. All classes are POJO.

The customer/supply model from jdonframework can seperate domain model from Persistence/Repository.

All business datas outside of domain is packed in a DTO anemic model(AnemicMessageDTO), so business rules in the aggregate root entity will not leak outside of domain.

avatar

These DTO anemic models can alseo be packed in Command and Domain Events,so they be managed in DDD ubiquitous business language.

  1. Rich in behavior

All business logic is located in Domain Model. No leaks to application layer or other places.

  1. Low level of primitive obssesion

Primitive attributes of Entites grouped together using ValueObjects.

MessageVO is a value Object, and has two attributes for message content: subject/body.

Clean architecture/Hexagonal architecture

JiveJdon is developed with JdonFramework that supports Customer/Supply or pub-sub model, this model can seperate domain logic from infrastructure, databases, other stuff.

avatar

JiveJdon Hexagonal_architecture:

avatar

here is package view of jivejdon:

avatar

Invoking path:

presentation -> api -> domain -> spi ->infrastructure

models.xml is a adapter for presentation:

	<model key="messageId" class="com.jdon.jivejdon.infrastructure.dto.AnemicMessageDTO">
		<actionForm name="messageForm"/>
		<handler>
			<service ref="forumMessageService">
			
				<createMethod name="createReplyMessage"/>
					
			</service>
		</handler>
	</model>

When a user post a replies message, a POST command from presentation will action the createReplyMessage method of forumMessageService in api :

public interface ForumMessageService {

	Long createReplyMessage(EventModel em) throws Exception;
	....
	
}

The forumMessageService will delegate the responsibility to the aggregate root entity ForumMessage,

The createReplyMessage() method of the forumMessageService will send a command to the addChild() method of ForumMessage that is too a command handler of CQRS:

avatar

@OnCommand("postRepliesMessageCommand") annotation make addChild() being a command handler, the annotation is from pub-sub model of jdonframework, it can make this method executed with a single-writer pattern - no blocked, no lock, high concurrent. only one thread/process invoking this update method.

"eventSourcing.addReplyMessage" will send a "ReplyMessageCreatedEvent" domain Event to infrastructure layer such as Repository. seperate domain logic from infrastructure, databases, other stuffs.

Domain event "ReplyMessageCreatedEvent" occurring in the domain is saved in the event store "jiveMessage", this is a message posted events table. the event can be used for reconstructing the latest replies state of a thread, events replay is in ForumThreadState .

CQRS architecture

CQRS addresses separates reads and writes into separate models, using commands to update data, and queries to read data.

avatar

In jivejdon ForumThread and ForumMessage are saved in cache, cache is a snapshot of even logs, if a update command activate one of these models, they will send domain events to clear the cache datas, the cache is similar as the database for query/read model, the consistency between with cache and the database for commmand model is maintained by the domain events such as "ReplyMessageCreatedEvent".

The domain event "ReplyMessageCreatedEvent" do three things:

  1. add a new post message to "jiveMessage" (events log)
  2. clear the query cache (CQRS)
  3. update/project the latest replies state of a thread (event project to state)

Event Sourcing

Posting a message is a event, modifying the latest replies status for one thread.

avatar

How to get the the latest replies status for one thread? we must iterate all posted events collection.

JiveMessage is a database storing posted events in time order, with one SQL we can reduce them chronologically to get the current state: the latest posted event:


SELECT messageID from jiveMessage WHERE  threadID = ? ORDER BY modifiedDate DESC

This sql can quickly find the latest replies post, similar as replaying all posted events to project the current state.

In jiveThread table there is no special field for latest replyies state , all states are from posted events projection. (projection can use SQL!)

When a user post a new ForumMessage, a ReplyMessageCreatedEvent event will be saved to event store: JiveMessage, simultaneously refresh the snapshot of event: ForumThreadState.

In ForumThreadState there is another method for projecting state from the database, if we want tp get the count of all message replies, its projectStateFromEventSource() method can do this:


	public void projectStateFromEventSource() {
		DomainMessage dm = this.forumThread.lazyLoaderRole.projectStateFromEventSource(forumThread.getThreadId());
		OneOneDTO oneOneDTO = null;
		try {
			oneOneDTO = (OneOneDTO) dm.getEventResult();
			if (oneOneDTO != null) {
				latestPost = (ForumMessage) oneOneDTO.getParent();
				messageCount = new AtomicLong((Long) oneOneDTO.getChild());
				dm.clear();
			}
		} catch (Exception e) {
			e.printStackTrace();
		}
	}

lazyLoaderRole.projectStateFromEventSource will send a "projectStateFromEventSource" message to ThreadStateLoader:

public void onEvent(EventDisruptor event, boolean endOfBatch) throws Exception {
		try {
			ForumMessage latestPost = forumAbstractFactory.getMessage(lastMessageId);

			long messagereplyCount;
			long messageCount = messageQueryDao.getMessageCount(threadId);
			if (messageCount >= 1)
				messagereplyCount = messageCount - 1;
			else
				messagereplyCount = messageCount;

			OneOneDTO oneOneDTO = new OneOneDTO(latestPost, messagereplyCount);
			event.getDomainMessage().setEventResult(oneOneDTO);

		} catch (Exception e) {
			e.printStackTrace();
		}

	}

ThreadStateLoader will reconstruct current state by SQL from MySQL database, the sql is "select count(1) ...". and now we refreshed the current state of a ForumThread: the count for all message replies.

Domain model mapping to the database schema:

avatar

Most of stuffs in aggregate root "ForumThread" mapping to jiveThread table, but its "rootMessage" mapping to jiveMessage table, and its state "ForumThreadState" is projected from jiveMessage table. In jiveMessage table there are two kinds of ForumMessage: root message and replies messages, one thread only has one root message, but has many replies messages, these replies messages are replies-posted event log. in domain model,repliese messages (FormMessageReply) is a sub class of Root Message(FormMessage).

Install

Docker:

  1. mvn package
  2. docker build -t jivejdondb -f Dockerfile.db .
  3. docker run -p 3306:3306 -e MYSQL_ROOT_PASSWORD=123456 jivejdondb
  4. docker build -t jivejdonweb -f Dockerfile.web .
  5. docker run -p 8080:8080 jivejdonweb

browser : http://$DOCKER_HOST_IP:8080

Document

english install doc

chinese install doc

chinese design doc

You can’t perform that action at this time.