Online for 7959 days
Last update: 1/4/11, 9:20 AM
| May 2024 | ||||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 | |
| November | ||||||
time to move! Antville is a symatic community but I'm...
Post is THE company which implemented SOA the first time,...
Hypothesis: Since infrastucture code is not part of the domain...
this time It's the content, stupid http://www.joost.com/home?playNow=33l83ke#id=33l83ke
interface. I'm sceptical http://news.cnet.com/8301-17939_109-10065136-2.html
gives to the Pattern Movement Look what I've found: A...
Alexander—The pattern language that we began creating in the 1970s...
hill in the morning mist. Nasim Taleb explains the...
Roland Kofler's Blog on Software Engineering on
The fallacy of a "technical" Domain Model
Today I came to the notion of a "technical" Domain Model, by a smart colleague by the way. Domain Model being synonym to "Model of a Domain" inherently is pure business, although I conceal that certain properties - the way it was modeled - reflects technical constraints. I already was able to optimize the performance of a system by optimizing the Domain Model. But no Aggregate, no Entity, no Relationship in a Domain Model can be represent a technical term. This is easily arguable for the core entities like Customer, but why should the Business Concept of a Searchquery not shaped by inquiring the analyst/business owner defining the business of the queries: do they have subqueries, would they be savable, do we have special operations on queries? The same goes for legacy boundaries. What means it interact with the legacy FROM BUSINESS point of view. If its important its business, not technical. That's what shapes the difference between an iPhone and a Smartphone.