I need help modeling this scenario. A Patient can have many medics A Medic can have many patients. A Patient is also a User. (MembershipUser)
I\'m struggling to get my head around what should happen whe开发者_C百科n rebuilding the model by replayingevents from the EventStore, in particular when events may trigger other events to happen.
I want to wrap id in custom class. Like this @Entity @Table(name = \"USERS\") public class User { @EmbeddedId
As 开发者_JAVA百科it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expertise, but this question will likely so
I\'ve asked a previous question last month, about whether an Entity should access a Repository, and although it looks like most people think they shouldn\'t, I have to admit it\'s hard for me to get c
Despite having studied Domain Driven Design for a long time now there are still some basics that I simply figure out.
I am quite confident with developing DDD applications, but one area which is continuing to cause me problems is when two applications integrate with each other. I am struggling to find any useful book
while designing my api, i am thinking about how i would like to model the following behavior. option 1 seems more logical, but with that comes enforcing invariants such as checking if the spreadshee
I have an 开发者_如何学运维aggregate root \'Order\', and it has a number of methods on it which internally set its \'Status\' field:
Is there way to map immutable Value objects like email address using JPA? @Immutable @Embeddable public final class EmailAddress {
加载中,请稍侯......