I would really appreciate peoples opinions on the below design problem. I have a model in which either a ‘Person’ or a ‘Business’ may be the provider of a certain ‘Service’. An example class d
I am building a middle size system and I am facing a problem that probably some of you have faced before. In my business layer I return business objects with a subset of properties that are important
My ORM is generating objects reflecting the database table structure. This objects are extensible, so I\'m able to add new properties and methods. This objects do not contains any persistence logic,so
I know that domain logic should be placed into domain objects. But what if my domain logic needs data from the database ? (e.g. checking unique value, computed values.. etc ) I think injecting reposit
I need some tangible guidance on implementing list of value objects in my distributed DDD application.Here\'s what I have:
I have read several articles online as well as several answers on StackOverflow about creating an audit trail for a database driven application.It seems that the most popular solution is to create an
I don\'t know so much about DDD repository pattern but the implementation in Spring is confusion me. public interface PersonRepository extends JpaRepository<Person, Long> { … }
I would like to find out if anyone can give me a hand on this problem that i am currently having. Basically, I have a legacy db that I have to deal with. I have created some domain classes to represe
I have POCO objects that reference each other by findi开发者_StackOverflow中文版ng ID\'s in repositories. I don\'t want the objects to have strong references between each other because the repositorie
I\'m facing a typical DDD problem. It must be very basic. I have an order and customer. A customer can create multiple orders. Customer is the root of its own aggregat开发者_运维百科e. Order is the ro
加载中,请稍侯......