架构概述

作者: 一路向北_c6e6 | 来源:发表于2018-10-07 19:57 被阅读0次

盖尔定律(Gall's Law)：
“一个切实可行的复杂系统势必是从一个切实可行的简单系统发展而来的。从头开始设计的复杂系统根本不切实可行，无法修修补补让它切实可行。你必须由一个切实可行的简单系统重新开始。”

企业级分布式应用服务 EDAS

理解 Istio Service Mesh 中 Envoy 代理 Sidecar 注入及流量劫持

A sidecar for your service mesh

Service Mesh 及其主流开源实现解析

What is Istio?

What Is a Service Mesh?

架构概述

http://ishare.iask.sina.com.cn/f/22378019.html

免费的计算机编程类中文书籍，欢迎投稿 http://weibo.com/justjavac

tcc saga
如何选择分布式事务形态（TCC、SAGA、补偿、基于消息的最终一致等等）

分布式事务的典型处理方式:2PC、TCC、异步确保和最大努力型

电子商务 - 维基百科
企业资源计划 - 维基百科
客户关系管理 - 维基百科
供应链管理 - 维基百科
办公自动化 - 维基百科

企业应用集成
笔记：
企业应用集成（Enterprise Application Integration，EAI）是完成在组织内，外的各种异构系统，应用和数据源之间共享和交换信息和协作的途径，方法学，标准和技术。
企业应用集成所连接的应用包括各种电子商务系统，企业资源规划系统，客户关系管理系统，供应链管理系统，办公自动化系统，数据库系统，数据仓库等。
EAI的原则是集成多个系统并保证各个系统互不干扰。

微服务架构

《企业IT架构转型之道：阿里巴巴中台战略思想与架构实战@www.java1234.com.pdf》

《10 Hottest Tech Skills To Master In 2016》

1. Cloud Computing
2. Network & Information Security
3. Big Data
4. Application Development
5. Data Mining
6. DevOps
7. Project Management
8. Business Intelligence
9. Data Engineering & Data Warehousing
10. Perl, Python, Ruby

《Java程序性能优化让你的Java程序更快、更稳定.pdf》

《Spring Cloud与Docker微服务架构实战 ,@www.java1234.com.pdf》

《Java高并发编程详解@www.java1234.com.pdf》

《《深入理解Spring Cloud与微服务构建》@www.java1234.com.pdf》

《设计模式的艺术--软件开发人员内功修炼之道@www.java1234.com.pdf》

《领域驱动设计：软件核心复杂性应对之道（修订版）@www.jqhtml.com.pdf》

《[www.java1234.com]分布式算法导论（原书第2版）.pdf》

《互联网企业安全高级指南.pdf》

《架构之美(清晰中文完整版).pdf》

《Applying UML and Patterns 3rd Edition.pdf》

《企业应用架构模式(中文版).pdf》

《高性能网站建设指南.pdf》

《Domain+Driven+Design%28领域驱动设计%29.pdf》

《I Heart Logs Event Data, Stream Processing, and Data Integration.pdf》

《《领域驱动设计》精简版.pdf》

《大型网站技术架构：核心原理与案例分析.pdf》

《亿级流量网站架构核心技术+跟开涛学搭建高可用高并发系统%40www.java1234.com.pdf》

《领域分析方法及技术的讨论.pdf》

《大型分布式网站架构设计与实践.带目录书签.完整版.pdf》

《微服务设计.pdf》

《Java RESTful Web Service实战 [韩陆].pdf》

《Building_Microservices_Nginx.pdf》

《软件架构模式.pdf》

《UML和模式应用（原书第3版）.pdf》

《分析模式-可复用的对象模型 .pdf》
《分析模式——可复用的对象模型%28注释版%29%40www.jqhtml.com.pdf》

解决方案 -- 网络基础架构，网络安全，数据中心和 IT服务管理

《领域驱动设计模式、原理与实践%40www.java1234.com.pdf》

《[www.java1234.com]软件构架实践_第二版_林_巴斯等著.pdf》

《大型网站系统与JAVA中间件实践www.java1234.com.pdf》

《优秀架构师必须掌握的架构思维.pdf》

1. 抽象思维
2. 分层思维
3. 分治思维和集成思维
4. 演化思维

《软件架构的艺术.pdf》

The top 5 software architecture patterns: How to make the right choice

1. Layered (n-tier) architecture
2. Microkernel architecture (Plug-in architecture)
3. Microservices architecture
4. Space-based architecture (Cloud architecture )

《software-architecture-patterns.pdf》
《软件架构模式.pdf》

《企业应用架构模式(中文版).pdf》

Web Architecture 101

The basic architecture concepts I wish I knew when I was getting started as a web developer

Books in Software Architecture

Books on the theory of Software Architecture

🥇Software Architecture in Practice (3rd Edition) (SEI Series in Software Engineering)

by Len Bass, Paul Clements, Rick Kazman

The first book in the list, as well as the first book which you should read on the subject of software architecture. This book describes the basic concepts: management of project requirements, especially non-functional, documenting the architecture, assessing the architecture in terms of success. It also clarifies how to work on architecture in agile terms and changing requirements. Examples and an easy-to-read style of writing are good advantages of this book.

🥈Essential Software Architecture

by Ian Gorton

One of the alternative books for your acquaintance with the basic theory giving a good overview of the software architect’s work. It describes the key skills which are needed to be an architect, from the way of thinking to the knowledge of various technologies. Also, there are considerations on the attributes of quality and other areas of software architecture.

🥈Patterns of Enterprise Application Architecture

by Martin Fowler

A wonderful book, which describes the cases that developers of enterprise applications have to deal with, as well as ways to solve those issues. One of the advantages is that the proposed solutions can be applied to many different technological stacks. However, in general this book is more suitable for a developer or a system architect than for a solution/enterprise architect, since it describes low-level problems and solutions.

🥇Domain-Driven Design: Tackling Complexity in the Heart of Software

By Eric Evans

This book is a must if you do not understand why it is a deadly sin to have the word “car” in the documentation, “automobile” in the implementation of the back-end database, and “vehicle” on the client side. Besides, it contains useful guidelines on how to communicate in order to get a working conceptual model and to orchestrate it for all of the stakeholders.

🥇Stakeholder Theory: The State of the Art

by R. Edward Freeman, Jeffrey S. Harrison, Andrew C. Wicks, Bidhan L. Parmar, Simone de Colle

The authors offer reviewing their great practical experience in understanding the needs of the modern business from the point of view of stakeholder management. The book describes both the basics and specific examples from various business domains, such as finance, accounting, law, management, and so on. Particular attention is paid to business ethics in cooperating with the stakeholders. This is one of the key books for changing the mindset: it helps to realize that everything should be done to solve people’s problems in the first place, but not because the developers need to practice the technologies.

Books about Design and schemes in Software Architecture

🥈Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development

by Craig Larman

UML is one of the generally accepted and popular standards of documentation in the development and architecture of software. The book gives many examples of how to draw UML diagrams. The author gradually shows what skills are necessary for documenting, each time complicating the task. The only drawback for the software architect is that most of the examples in the book are about object-oriented programming, and they are not related to high-level schemes for large projects.

🥈Documenting Software Architectures: Views and Beyond

by Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Paulo Merson, Robert Nord

This one is a real classic in the field of documenting software architecture. It is the most comprehensive guide answering the questions from “Why do I need documentation at all?” to “How to document SOA”. Besides, it explains various documentation techniques (UML, AADL, and SySML) along with real-life examples.

🥉Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

by Nick Rozanski, Eóin Woods

The authors of one of the best known and most frequently used techniques for designing and documenting software architecture offer their vision for these processes. At least you will learn an alternative approach to designing and documenting, at most you will apply it to your project.

🥈Designing Software Architectures: A Practical Approach (SEI Series in Software Engineering)

by Humberto Cervantes, Rick Kazman

This book can help you adopt various designing methodologies from real-life projects. One of the key points of this book is the description of ADD (Attribute-Driven Design) and the application of this approach to practice. The authors also introduce different principles of designing in relation to different projects, from pre-sales to enterprise solutions.

Other books on Software Architecture

🥇Software Estimation: Demystifying the Black Art

by Steve McConnell

The author of “Code Complete” shares the secrets of evaluating projects of any size and degree of uncertainty. This book is as suitable for the developer, like the architect or manager. It contains a huge number of assessment techniques and allows you to understand your current level as an assessor of projects. A must-read!

🥉Enterprise Architecture As Strategy: Creating a Foundation for Business Execution

by Jeanne W. Ross, Peter Weill, David Robertson

The book is for those who want to learn more about the enterprise architecture and to understand interrelations between the business and the nature of solutions for it. The authors’ overview of the company’s business and its connection to IT inside the company will allow you to understand why the choice is made in favor of this or that solution, and also how to arrange IT processes so that they work for business.

🥉Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems

by Martin Kleppmann

The author shares his experience in building scalable, stable, and flexible systems. The book describes the key principles of building such systems, as well as examples of workarounds which may be unavoidable during the design.

Architecting Software Intensive Systems: A Practitioners Guide

Quality attributes in Software Architecture. Part I

Quality attributes types (ISO/IEC FCD 25010 diagram)
To consider the types of quality attributes, we can use a diagram from ISO 25010:

Image 2. ISO/IEC FCD 25010 diagram

The Path to Becoming a Software Architect

First, let’s consider the characteristics of the architect:
● Communicability.
● Broad and deep technical knowledge.
● Responsibility.
● Stress resistance.
● Management skills.
● Analytic skills.

How to Become a Software Architect?
To begin with, it is important to define milestone goals that lead to achieving your strategic goal of becoming a software architect. For me, such goals for the next six months are:
● Understand and try several technological stacks.
● Reading literature.
● Find a mentor
● Study courses/obtain certificates.

Software Architecture Methodology and Concepts