Tribute to the software architect Master

Recently in the study of enterprise-class software architecture design, selected on the Chinapub, to buy two copies:

"Patterns of Enterprise Application Architecture", by Martin Fowler

"Microsoft.NET:Architecting Application for the Enterprise" by Dino Esposito & Andrea Saltarello

Martin Fowler, his refactoring, his UML distilled, often read his words, is absolutely clairvoyant, should let people produce "holding the hand, and the son of the" impulse. (Don't think crooked, I am pure man, not gay)

Martin Fowler and Kent Beck are the gurus of my esteemed agile development field. In terms of language development, the older brothers seem to prefer Smalltalk and Java.

Over there Anders Hejlsberg a listen to this quasi-do not agree: "I, my home old pimple C # is stepmother to raise it?" Uncle Anders, do not get angry, I have been with you mixed, contented it!

Anders but I most the most most worship of the development of language Design Master Ah, is not there a sentence? "born son when like Anders"!

That year gates but open the luxury and grow up limo blatant to Borland headquarters dug Anders Ah

Said the stray bird, hurriedly pull back.

Martin Fowler the Fowler on the lake (no Martin wanted to be different from Robert C. Martin, another agile development guru).

Dino Esposito, this xiaomianhu general Italian guy is not really covered, ASP. NET aspect of the Danale, written in English humor and fluency, the former words can be seen.

Dino Esposito Lake Dino.

Although Fowler's book is easy to understand can be compared to Bai Juyi's poetry, but after all, this is the Jolt Grand Prize of the Classics, the scope of the topics covered is also large enough to let me have awe, Leng did not dare to direct.

And Dino's book is both Microsoft and. NET label, and Fowler is about the same kind of problem, it would be easier. Let's get started with it, then Chew Fowler.

Practice has proved that my initial judgment is also not wrong drop.

Dino the first three chapters on "Architects and Architecture", "UML Essentials", "Design Principles and Patterns" have a wonderful narration, the code is also short precise, the reading experience is very good. But in the fourth chapter "the Business Layer" in a talk domain Model pattern let my heart start whispered, until see summary face I also still confused:

Since domain model is highly abstract about the underlying data wrapper and related operations, who is going to model the business that the user cares about? What can you do to make sure that the business layer with the domain Model pattern is true? I didn't find an answer to the fourth chapter.

Fortunately Dino mentioned that the model used in the business layer was derived from Fowler's masterpiece and marked the page numbers of each model in the book.

It seems that I had to turn to Uncle Fowler. Turning to the 116th page specified is a description of the domain Model pattern. But as I looked through the catalogue, I found that there was a chapter "organizing Domain Logic" that started on page 25th. Since it's an umbrella, let's start with page 25. You can see the real thing on this one. Fowler first emphasized the existence of a service layer: a common approach in handling domain logic was to split the domain layer in. A service layer is placed over an underlying domain model or table module ... The presentation logic interacts with the domain purely through the Service Layer, which act as a API for the application . Finally, it points out: My preference is thus to having the thinnest Service Layer can, if you even need one. Reading this, the previous doubts vanished, carefree dripping!

Back to see Dino's book, the fourth chapter "the business layer" after actually followed a fifth chapter "the Service Layer", which also expressed and Fowler the same meaning. Although from the whole, Dino did not omit knowledge points, but the layout of the defect in the article when really let me depressed a.

His flaws, Dino's book is still very good, the other 3 modes in the BLL: Transaction Script, Table module, and active record are all very clear.

After all, or Fowler comrade Chess recruit Ah. Maybe he should have done it in the first place? Who knows!

It is so-called:Dino True ox man, Fowler Pure master.

Tribute to the software architect Master