- A Step Toward Realism
- Overview
- New Architecture Code Examples
- The Usual Type of Client-Side Code
- A Couple of Tweaks that Help Performance
- Collapsed Objects
- Statuses in One Single Byte
- Object Vector
- NonSerialized()
- Using "Dumb" Collections
- Another Struggle with Guids
- Oops, Maintainability Must Be Lost!
- And a Few Tweaks Not Applied Yet
- A New Test Application
- Results of the Throughput Tests
- Conclusion
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Overview
The EntityBase is found in a layer called the Domain Model. In Figure 2, you see an overview of the different layers in the new architecture.
)
Figure
2 Overview of new architecture.
As shown in the figure, one way to use the Domain Model is to let the client work directly with it. But there is nothing stopping you from letting the client work only with Data Transfer Objects instead. (See Fowler, Patterns of Enterprise Application Architecture.) What I mean is that this discussion is important, no matter what you let the client interact with.
As you get a feeling for Figure 2, this time there is a lot more code that will cooperate to provide the result (actually, too much for those simple tests, but beneficial for real applications). What is the extra code? Stay tuned.