What are the principles behind, and benefits of, the “party model”?

by
  1. What are the core principles and motivating forces behind the party
    model?

To the extent that I’ve used it, it’s mostly about code reuse and flexibility. We’ve used it before in the guest / user / admin model and it certainly proves its value when you need to move a user from one group to another. Extend this to having organizations and companies represented with users under them, and it’s really providing a form of abstraction that isn’t particularly inherent in SQL.

  1. What does it prescribe you do to your data model? (My bit above is
    pretty high level and quite possibly
    incorrect in some ways. I’ve been on a
    project that used it, but I was
    working with a separate team focused
    on other issues).

You’re pretty correct in your bit above, though it needs some more detail. You can imagine a situation where an entity in the database (call it a Party) contracts out to another Party, which may in turn subcontract work out. A party might be an Employee, a Contractor, or a Company, all subclasses of Party. From my understanding, you would have a Party table and then more specific tables for each subclass, which could then be further subclassed (Party -> Person -> Contractor).

  1. What has your experience led you to feel about it? Did you use it, and if
    so, would you do so again? What were
    the pros and cons?

It has its benefits if you need flexibly to add new types to your system and create relationships between types that you didn’t expect at the beginning and architect in (users moving to a new level, companies hiring other companies, etc). It also gives you the benefit of running a single query and retrieving data for multiple types of parties (Companies,Employees,Contractors). On the flip side, you’re adding additional layers of abstraction to get to the data you actually need and are increasing load (or at least the number of joins) on the database when you’re querying for a specific type. If your abstraction goes too far, you’ll likely need to run multiple queries to retrieve the data as the complexity would start to become detrimental to readability and database load.

  1. Did the party model limit your choice of ORMs? For example, did you
    have to eliminate certain ORMs because
    they didn’t allow for enough of an
    “abstraction layer” between your
    domain objects and your physical data
    model?

This is an area that I’m admittedly a bit weak in, but I’ve found that using views and mirrored abstraction in the application layer haven’t made this too much of a problem. The real problem for me has always been a “where is piece of data X living” when I want to read the data source directly (it’s not always intuitive for new developers on the system either).

More Related Contents:

  1. Best way to model Customer Address
  2. Recommended SQL database design for tags or tagging [closed]
  3. Are soft deletes a good idea? [duplicate]
  4. What mysql database tables and relationships would support a Q&A survey with conditional questions? [closed]
  5. single fixed table with multiple columns vs flexible abstract tables
  6. DB design to use sub-type or not?
  7. Relational database design question – Surrogate-key or Natural-key?
  8. How to implement a many-to-many relationship in PostgreSQL?
  9. How to implement one-to-one, one-to-many and many-to-many relationships while designing tables?
  10. What is the purpose of system table master..spt_values and what are the meanings of its values?
  11. Using an ORM or plain SQL? [closed]
  12. What are best practices for multi-language database design? [closed]
  13. Database Structure for Tree Data Structure [closed]
  14. Database Design for Revisions?
  15. A beginner’s guide to SQL database design [closed]
  16. PostgreSQL: Which Datatype should be used for Currency?
  17. Why (and how) to split column using master..spt_values?
  18. Is there common street addresses database design for all addresses of the world? [closed]
  19. JPQL IN clause: Java-Arrays (or Lists, Sets…)?
  20. Dynamic Database Schema [closed]
  21. How to create a multi-tenant database with shared table structures?
  22. When to Denormalize a Database Design
  23. SQL ON DELETE CASCADE, Which Way Does the Deletion Occur?
  24. PostgreSQL Index on JSON
  25. SQL: Using NULL values vs. default values
  26. What is the best way to implement soft deletion?
  27. Is there a severe performance hit for using Foreign Keys in SQL Server?
  28. How important are lookup tables?
  29. Historical / auditable database
  30. Designing SQL database to represent OO class hierarchy

Leave a Comment