New book reading-software castle-enterprise structure modeling

I recommend a book to everyone. I don't think it's just my own thoughts.

 

Software castle-Enterprise Structure Modeling Higher Education Press Author: Roger sessionsPricing: 18.00 RMB

English name: Software fortresses: modeling enterprise ubuntures

I rated it on my own3About half a star4Star, that is, Accuracy4Star, I hope the following comments will explain my comments

 

fortress A very uncommon word, but it is very appropriate to use, I checked Kingsoft, compared to chateau, castte, castle these words fortress more accurate, I like Software fortresses you may feel the same after reading this book, I also recommend that you go to Roger articles .

In addition, I don't want to introduce it.Roger sessionsTo add more space, many book reviewers are willing to use the author of the book to influence the choice of readers. Many times, when I read a book, I first look at the Directory and the structure of the book, then I think about the value it brings to me. The author is often the last to be noticed. I hope you can read this book as well.

 

We are talking about SOA What is SOA , A pair of confused eyes, it is easy to think 3 What were we talking about years ago? . Net In the age of, there were hundreds of exchanges and lectures from different angles and methods. However, the audience often sprayed the demonstration and saliva over an hour and told themselves with suspicion. . Net ? It's almost an emperor's new outfit mixed with Alice Wonderland's emotions. Maybe many people 3-5 Years later . Net With my own opinions, some even gave up the pursuit of the meaning of this word, . Net- This is an advertisement word. It's cool, but some people are right . Net .

HoweverWeb ServicesTheir feelings are so strange that today they are looking at them again with a feeling of mutual respect.SOAI believe they have ignoredWeb ServicesOr get tired of knowing what it is.

There are also so-called design patterns, refactoring,XP,TDDI will feel very warm and satisfied with such a book and concept, maybe you have a chance to summarize and accumulate the image of the software and software architecture you have understood before. Maybe this will be a great benefit for you to welcome the so-called bright tomorrow, this book can bring you different perspectives.

 

The concepts of software Castle, hanging bridge, guard, city wall, special envoy, treaty, and Alliance are proposed. I think they are very novel and practical. Actually, we all know the concepts of these technologies, however, the role and illustration of these dramas are more understandable and constructive.CTOOr the role of the architect to a group of developers, designers, or evenProgramYou will have more confidence in your understanding of the software architecture. Afterwards, you may be described as a thoughtful Software Architecture expert.-This is another value beyond the technical value of this book.

 

The author was honest and he wasPat HellandA so-called autonomous computing model, software Enclosure(Software fidfdoms)The impact of ideas, and I found that the author has raised some very important concepts that may be ignored by everyone now, such as transaction processing, synchronous and asynchronous methods,WebAuthorization, security, and integrity of methods. How to re-consider and design these obscure elements in the design and new concepts remains a difficult part of the enterprise application architecture. From the perspective of enterprise application architecture and technology Architects, the author gives a lot of suggestions and practical opinions on what basic principles should be followed.

 

This is another feature of this book. It highlights the topic of building a conceptual model for an enterprise application system. At the same time, it also brings you a detailed discussion of one element, so that you can only feel that, this book is still too thin. You can read it by train from Guangzhou to Shenzhen, but I believe that if you do not read it several times, you can hardly fully understand the author's intention. Understanding architecture is better than understanding design patterns andTDDI believe that if you do not fully believe in this theory and experience it in person, you will not be able to grasp many concepts and principles in the book, it cannot even help you with the project or application architecture.

 

Of course there are also some failures in the book, such as the author's design and modeling methods J2EE The impact of the platform on transactions and high reliability Microsoft Traces of the platform. There are also many sections in the book . Net vs. J2EE Of course, as the author's identity, this may be a problem that he is often asked by his customers. In the end, he means to tell the customer that the software Castle is not a solution and proof. . Net And J2EE Advantages and disadvantages. It depends on your own situation. If you don't know anything or only know . Net Or J2EE The author's point of view is helpful, just like his assumption, but if you already have your own point of view, then you may feel a little redundant. Afterwards, I think these descriptions may be necessary, because at least as an architect, this is a realistic and feasible way, the evaluation, selection, security, interaction, and interoperability of the technical platform must be directed and concluded by the architect.

 

The whole book understands youSOAAndModelingThe architecture is very helpful, otherwise many people will not be able to quickly switch from the current architecture to fuzzySOAIn terms of architecture or concept, in addition, according to the definition of martial arts realm, if you cannot break the old concepts and system architecture in your head, it is also difficult to accept new concepts and open the second pulse of Ren du, after all, sometimes we have fixed the concept of architecture, and we have been devoted to design patterns and reconstruction that are too detailed for a long time. With confidence, it is hard to go back to the bank at the moment.

 

I prefer the last chapter. In addition to summing up, demonstrating, and looking forward, the author has enough courage to answer some embarrassing questions and express his opinions in good faith, such15.6The author of this section said that the following is my dissatisfaction with the current status of the software industry:

• The software industry lacks a conceptual model for establishing enterprise systems
• The software industry lacks a consistent view on the transactions that run through the Enterprise.
• The software industry is a mess in terms of security capabilities and lacks corresponding application models.
• When we need interoperability standards, the software industry is wasting time on portability standards.
• Independent Implementation Technology in the software industry(For example, Object), Distributed technology(For example, Components)And Interoperability Technology(For example, Castle)
• The software industry does not distinguish between communication occurring within the system and between systems.
• The software industry does not have a common interoperability model, so it is difficult for different vendors to combine the products.
• The software industry uses the Hong Kong terminology of technology to describe the work it has done, which makes it difficult for the Party to communicate and understand each other when using a common approach.
• The software industry assumes that interoperability issues will be addressed through a single technology that can be consolidated
• The software industry usually provides concepts or technologies that are not only useless but completely harmful.

 

Let alone whether these problems are correct or wrong. If you carefully look at the descriptions of each problem in the book, you will find that these problems are very good, anyone who dares to call himself a famous software architect is a test and difficulty for him.

 

After reading the book, I think of the previous scenario of playing the Empire era. When can the software architecture be as good as a strategic game in the Empire era, or the software architecture is always the same as the strategic game, it's just that we never feel immersive.

 

The original blog post is copyrighted. The source must be indicated for reprinting.