1,636 reputation
1030
bio website deslondesoftware.com
location Walnut Creek, CA
age 36
visits member for 3 years, 11 months
seen Dec 15 at 21:22

I love this site. I am here to learn, and try to contribute back as much as possible. Feel free to contact me at rdeslonde@deslondesoftware.com.

As an aside, I can't thank everyone on this site enough for their answers. This site (and it's sister sites through SE) are INVALUABLE.


Aug
12
awarded  Notable Question
Aug
6
answered What can REST API do that a API using HTTP URL query strings cannot do?
Mar
26
awarded  Popular Question
Mar
22
awarded  Popular Question
Feb
17
awarded  Nice Answer
Feb
15
awarded  Popular Question
Jan
30
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
The data sets are enormous and the aggregations require a lot of calculations. Doing this on the fly at every time a change is made to the domain is not an option. It would be impossibly taxing on resources. The reports look at the data from a lot of different angles. Maybe I could split it between basic database queries and queries that have a lot of BL, and just preaggregate those that have a lot of BL. Seems strange no one really has an answer for this common scenario.
Jan
30
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
Not sure how this relates to my question or how it got 3 votes so fast. Also did you mean to include a link here?
Jan
30
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
@JanDoggen That's exactly my point. The BI tool will HAVE to have BL logic in it. Now I'm duplicating the BL that is in the rich domain of my software product. Is that OK?
Jan
30
awarded  Yearling
Jan
29
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
I'm confused. Has no one done this? No one faces this issue?
Jan
29
awarded  Nice Question
Jan
28
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
They don't modify the domain...so then all ETL processes and data transformations to create the data for the data warehouse have to go through your domain? Otherwise your BL is duplicated in all the logic of your ETL processes.
Jan
27
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
Hi Mike. I am very familiar with datawarehousing and BI, having been doing it for 15 years. My question deals with how to handle this in a domain driven design context. Are datawarehouses ok? Or are they an adulteration of your domain business layer? If the answer is build a data warehouse and pull the data from there, there is a lot of literature and advice out there for that. But then you are duplicating business logic outside of your domain. Is that ok? That's my question.
Jan
26
revised Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
added 540 characters in body
Jan
25
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
And do you go through your business layer/domain to obtain all this information in every display/report? Or do you pull from these tables?
Jan
25
revised Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
added 123 characters in body
Jan
25
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
Hi Christian, I'm glad to see I'm not the only one struggling with this. Thanks for your answer. See my comments on Marcocs answer for the problems I see with this approach. Any ideas on dealing with those would be appreciated!
Jan
25
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
I'm interested in this approach but it presents a lot of problems to my mind.
Jan
25
comment Best practice or design patterns for retrieval of data for reporting and dashboards in a domain-rich application
...changes for example hours added or subtracted. Etc. The list goes on. As far as #2 the aggregations needed...tomorrow the customer needs to see aggregations by region, then they want to see by employee, or by city, or industry, or any other crazy attribute on the project or related entity. Will you pre-aggregate all of these? If so, now you are creating an OLAP engine...Also, do these aggregations belong stored in the project Object in the domain? When you present the data, when will you use a calculated value vs the precalculated value. Etc. Have you made this work in a real world app?