Hot answers tagged

6

It depends on what you're willing to do in terms of architectural/performance payoffs. It sounds like at the core you're doing a kind of Event Sourcing, which actually makes a lot of sense when you start talking about domains where it's important to have audit-trails for exactly what happened. I think a key-point for avoiding "code rot" is to make sure that ...


1

I'm wondering if what you are trying to do is actually going to make things extremely difficult. Specifically what you say about coupling the data to an existing SQL server DB. This makes me think you want to effectively run two databases. Whilst doable, issues with querying, synchronisation and performance will result in large amounts of code, bugs and ...


1

First, three observations. Already covered by Christophe in the previous answer: the table that controls the flow to another question group needs to have the QuestionID as a foreign key. Otherwise the answers "Yes" or "Dogs" can't be related to a question. I would change the terminology from "ParentGroup/ChildGroup" to "QuestionGroup/FollowingGroup", ...


1

Questions templates or question instances ? Your question shows an ambiguity in the conceptual model: do you manage question instances ? In this case one QuestionId means one single question that could eventually be triggered by several events, but only one answer is relevant, regardless of the way you activate it. That's what your data model suggests. ...


1

When you only needed to deal with Transactions, then a single Transactions table was sufficient. Now you need to know about summarisations at the Account level. Yes, you could calculate these dynamically, but this will get progressively slower the more Transactions you have to trawl through. This isn't a User Experience decision. How often will a User ...



Only top voted, non community-wiki answers of a minimum length are eligible