Before I had an article, " look at the software architecture from the perspective of practitioners of history ", mainly from the macro point of view, from a comparison of industry and academia on the software architecture research to illustrate the historical changes and the future of software architecture for 25 years trend.
After that, I Thinking again, there is no summary report for development of software application architecture it, it is best explained mainstream application architecture and application scenarios, in doing so architects architecture design, it can be a lot of reference. You do not say, I really found the "Software architecture patterns", PDF documents more than fifty pages, describes the application architecture and mainstream usage scenarios for each architecture agility, ease of development, testability, and ease of deployment aspect, scalability, and performance was evaluated. There are also several online this report by simply reading the article, but I saw all thought that it was not very careful. Originally I wanted to translate that document directly, but considering the more than fifty pages, spend more time, and recently our products to be on the line, not enough time to squeeze, so I wanted to understand the will learn some of the translation himself and slightly At the same time the article written means, thus reducing the space to deepen their understanding of architecture may also be able to make friends some insights. Obviously, this is beneficial to all things, what I waiting for? So after finishing the day's work, I Jing Xiaxin, his insight, thoughts codes into text, then you will see this article.
Some people may be wondering why I always tend to focus on relatively ambitious proposition. I can only say, maybe it comes from the fear of it no sense of direction, and indeed useful knowledge, of course, if you usually just develop some small official website, I have to admit that you might not use, do not understand it anyway.
Although this painstaking long article is free, but I still put people to grow [technical] knowledge shop, because [technology] people growing community there are also many readers, there may not have a lot of public concern number or technical blog, put there to facilitate them to read, and a long article, so I do not have to worry about editing again.
By the way everyone was introduced to [grow] technical people spread knowledge of it, this is my knowledge to open a shop, there are some paid content I produced myself, and my selection of some of the other techniques cattle paid work, but the part or free, including the knowledge of the planet is similar communities also are free, mainly to get to know more friends, colleagues, the public is also welcome number of our readers a lot to the community in exchange.
Micro-channel scan code to read the full article, you can also enter [technical] people to grow the community around.
