I am not able to clearly understand the problems of bottom up approach against which Domain Driven Design advocates. Can someone please write briefly or nudge me in the write direction? What I mean is, in Sql world we have entities represented by tables, they have relations, constraints and so on. So now how is the new approach of starting with classes as entities as proposed by DDD will benifit us? But before that, as the questions indicates, I need to understand the problems posed by bottom up approach.
What are the problems with bottom up approach
588 Views Asked by VivekDev At
1
There are 1 best solutions below
Related Questions in DOMAIN-DRIVEN-DESIGN
- Add image to JCheckBoxMenuItem
- How to access invisible Unordered List element with Selenium WebDriver using Java
- Inheritance in Java, apparent type vs actual type
- Java catch the ball Game
- Access objects variable & method by name
- GridBagLayout is displaying JTextField and JTextArea as short, vertical lines
- Perform a task each interval
- Compound classes stored in an array are not accessible in selenium java
- How to avoid concurrent access to a resource?
- Why does processing goes slower on implementing try catch block in java?
Related Questions in BOTTOM-UP
- Add image to JCheckBoxMenuItem
- How to access invisible Unordered List element with Selenium WebDriver using Java
- Inheritance in Java, apparent type vs actual type
- Java catch the ball Game
- Access objects variable & method by name
- GridBagLayout is displaying JTextField and JTextArea as short, vertical lines
- Perform a task each interval
- Compound classes stored in an array are not accessible in selenium java
- How to avoid concurrent access to a resource?
- Why does processing goes slower on implementing try catch block in java?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
In SapiensWorks Mike explain it very well:
I suggest you to read the complete post before continue reading here.
If you design persistence schemas first you are not taking Domain into account; not completely and with the deep needed, at least. You are designing for efficience, redundancy, normalization, relations, etc not behaviour and later you will create entities that fits into that persistence scheme. Suddenly, you will find meaningless, strange and weird things done in your entities just to match persistence schema, persistence implementation and/or persistence technologies unless you make iterations of persistence redesign.
Both aproaches, entities designed to fit persistence and persistence redesign iterations, are bad. The first one because bad entity design and SOLID breaks; the second one because is extra work and a waste of time.
Good entity design (what it means good Domain modeling) and/or not wastig time in persistence design iterations.