␡
- 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
< Back
Page 16 of 16
Like this article? We recommend
Conclusion
Without having to change to custom serialization, we get pretty good performance in the new architecture. With a couple of tweaks, we can save a lot of space when the serialized objects are moved over the wire, and that translates directly in better throughput. And thanks to the Layer Supertype pattern the tweaks won't cost that much when it comes to maintainability. (See Fowler, Patterns of Enterprise Application Architecture.)
< Back
Page 16 of 16