best enterprise architecture books

650) this.width=650; "Src=" Http://upload-images.jianshu.io/upload_images/5712789-6f048f20e4792433.png?imageMogr2 /auto-orient/strip%7cimageview2/2/w/1240 "style=" height:auto;vertical-align:middle;border:0px; "alt=" 1240 "/>You are welcome to study the relevant technology togetherSource source for complete projectsSpring,springmvc,spring mvc,web Development, Java distributed architecture, SHIRO,MYBATIS,KAFKA,J2EE distributed architectureThe essence o

Platform IntroductionJeesz is a distributed framework that provides modular, service-based, hot-swappable ideas for project-based Java EE Rapid development platforms with high package security.Jeesz itself integrates Dubbo service control, zookeeper Registration Center, Redis distributed cache technology, FASTDFS Distributed File system, ACTIVEMQ asynchronous message middleware, Nginx load balancing and other distributed technologiesProject management using MAVEN, Project modularity, improve pro

Statement: The framework for enterprises, is a large-scale Internet distributed enterprise Architecture, later on Linux on the deployment of high-availability cluster project.Project-based functionality (smallest part since provided)Introduced1. Project Core Code structureJeesz-utilsJeesz-configJeesz-frameworkJeesz-core-cmsJeesz-core-genJeesz-core-bookmarkJeesz-core-actJeesz-core-oaJeesz-core-testJeesz-core

, desktop applications and mobile phones.Particle-commonservice-turbine: is a tool for aggregating server to send event stream data to monitor the metrics situation of Hystrix under cluster and provide independent service project.Particle-commonservice-zipkin: Provides a standalone service project that enables a distributed tracking solution for Springcloud applications. The data flow of distributed tracking system is divided into three steps: collecting, sending and landing analysis, Zipkin the

This article from: http://www.cnblogs.com/yuyijq/archive/2010/03/13/1684938.html Martin Fowler, the enterprise application architecture model, should have been a household name. After buying it for a few days, he never picked it up. Now he has finally reached this book. This book is roughly divided into two parts. The first eight chapters are the first part, which gives a preliminary introduction

Design Mode: Simple factory Mode Factory method mode Abstract Factory method mode Singleton Mode Appearance Mode Generator Mode Original Mode Intermediary Mode Proxy Mode Observer Mode Command mode Iterator Mode Combination Mode Template Method Mode Rule Mode Status Mode Memorandum Mode Meta Mode Interpreter Mode Decorator Mode Responsibility Chain Model Bridging Mode Visitor Mode

Framework: MyBatisSecurity framework: Apache ShiroServer-side validation: Hibernate ValidatorTask Scheduler: QuartzLog management: slf4j 1.7, log4jClient-side validation: JQuery ValidationDynamic tab: EasyuitabFront-End frame: Bootstrap, Vue3. Design IdeasDistributed, microservices, cloud architectureJava language development, cross-platform, high-performance, high-availability, secure, service-based, modular, component-driven development model4. Platform Basic functionsUser management: The use

, was the chief operating officer of Quigo (advertising technology start-up, later acquired by AOL), responsible for leading product strategy, product management, technology development and customer service. He has worked on ebay for 6 years and has served as vice president of Technology, chief technology officer and company executive.Michael Fisher, aKF's start-up partner, was previously chief technology officer at Quigo, and PayPal was the vice president of engineering and

It is not only a means of doing business, it is rapidly evolving into a business, it performance will directly affect the profitability of the enterprise, but many enterprises do not have the timely or adequate involvement of the IT organization in the planning and decision-making process of the business, do not give the planning and IT decision-making process to consider the security, scalability, It issues such as integration issues are sufficiently

Today formally introduced the spring cloud-enterprise distributed micro-service cloud architecture, I have combined with most of the current enterprise general requirements, including the selection of technology is more stringent, harsh, not only to use the industry's most popular technology, but also with international standards, in the next 5-10 years can not o

Today formally introduced the spring cloud-enterprise distributed micro-service cloud architecture, I have combined with most of the current enterprise general requirements, including the selection of technology is more stringent, harsh, not only to use the industry's most popular technology, but also with international standards, in the next 5-10 years can not o

In the annual summary and plan: Last year 4 1, 5 1 This year, I said I am going to introduce an architectural party TOGAF to the project team this year. Yang Xueshan, vice Minister of industry and Information technology, said in an internal discussion: Compared with the Western developed countries, the domestic information construction in the hardware has been comparable, in the software has 5 years of disparity in information management has about 10 years of the gap in the

Design pattern: Simple Factory mode Factory method Mode Abstract Factory Method pattern Single case mode Appearance mode Generator mode Prototype mode Intermediary mode Agent mode Observer mode Command mode Iterator mode Combination mode Template method Mode Policy mode State mode Memo Mode Enjoy meta mode Interpreter mode Adorner mode Responsibility chain Model Bridging mode Visitor mode Enterprise Application

ArticleDirectory I. Review in the previous chapter Ii. Summary Iii. Contents of this Chapter Iv. Structure Diagram 5. behavior diagram 6. Summary in this chapter. VII. Progress of the series. 8. next announcement. Background I. Review in the previous chapter Previous Article: System Architect-Basic-to-enterprise application architecture-system modeling [Part 2] (Part 2)

the compilation phase, Complete the code implantation before compilation, and ensure that the embedded code can be compiled. For more information about piab, see the piab series enterlib piab deep analysis by artech. Vi. Summary in this Chapter This chapter describes in detail how to implement the specifications and principles of software design. The focus is separated by object-oriented and object-oriented programming, and the principles followed in the implementation process. And analyze

First, Oberzhang reviewFirst of all, we will review the contents of the previous article, deepen the impression. In the previous chapter we mainly explained the 3 modeling graphs are: Sequence diagram (sequence diagram), component diagram, State diagram.Specific function description such as: Here is not explained in detail, if not clear see: System Architect-Basic to Enterprise Application architecture-Syst

System Architect-Basic to Enterprise Application Architecture-IndexThe System Architect-Foundation to Enterprise Application Architecture series will range from the origin of the system architecture, development, the basic knowledge and skills of architects, and how to apply

Basic concepts FRAME (framework): is to deal with a certain type/certain aspects of the idea/approach, through a large number of early research, try, adjust, refine, validate, design and summarize a set of common, feasible methods and knowledge of the organizational structure, can help others to deal with similar problems. is a macro, high-level guidance, but the framework is not a standard answer, there is no direct result, need to understand the basis of flexible use.Methodology (Mehtodo

(Translator's order)"Each pattern describes a recurring problem around us and the core of the solution to the problem. In this way, you can use this solution again and again without repetitive work ." ---- Christopher AlexanderMoves can be ever-changing, but the solid and profound "internal strength" is consistent;(Preface)For books on the universality of software architecture, I recommend [POSA]-"pattern-o

(Translator's order)"Each pattern describes a recurring problem around us and the core of the solution to the problem. In this way, you can use this solution again and again without repetitive work ." ---- Christopher AlexanderMoves can be ever-changing, but the solid and profound "internal strength" is consistent;(Preface)For books on the universality of software architecture, I recommend [POSA]-"pattern-o