- Introduction
- De Architectura
- The Art and Science of Building
- Foundation
- Platforms
- Closed
- Open
- Interfaces
- Forces
- When do you need an architect?
- How Large?
- Software Architecture
- Lecture Context
- Why Software Architecture?
- Hiding Complexity
- Abstraction
- Communication
- Representation
- Visualization
- Quality
- Change
- Evolution
- De Architectura
- Quality Attributes
- Quality
- Functional, Extra-Functional Qualities
- Internal vs. External
- Static vs. Dynamic
- Meta-Qualities
- Quality Attributes
- Design Qualities
- Feasibility
- Affordability
- Slack
- Time to Market
- Modularity
- Reusability
- Design Consistency
- Simplicity
- Complexity
- Clarity
- Stability
- Composability
- Deployability
- Feasibility
- Normal Operation Qualities
- Performance
- Scalability
- Capacity
- Usability
- Ease of Support
- Serviceability
- Visibility
- Dependability Qualities
- Reliability
- Availability
- Security Qualities
- Defensibility, Survivability
- Privacy
- Change Qualities
- Flexibility
- Configurability
- Customizability
- Resilience, Adaptability
- Extensibility, Modifiability
- Elasticity
- Compatibility
- Portability
- Interoperability
- Ease of Integration
- Long Term Qualities
- Durability
- Maintainability
- Types of Maintenance
- Sustainability
- Quality
- Definitions
- Who is a software architect?
- Functional Organization
- Cross-Functional Organization
- Facilitate Communication
- Software Engineering Lead
- Technology Expert
- Risk Management
- Architect Tribes
- Software Architecture and the Software Development Lifecycle
- Bridge the Gap
- Think Outside the Box
- Evolutionary Model
- Agile Unified Process
- System Lifecycle
- Defining Software Architecture
- Architecture vs. Code
- Architecture vs. Technology
- Architecture vs. Design
- Basic Definition
- Design Decisions
- Design Process
- Design Decisions
- Decision Making Phases
- Decision Trees
- Design Outcome
- Modeling Architecture
- Can this skeleton fly?
- Prescriptive vs. Descriptive Architecture
- Green Field Development
- Brown Field Development
- Architectural Degradation
- Causes of Architectural Drift
- From Drift to Erosion
- Entropy
- Architecture or Code First?
- Architecture Hoisting
- Presumptive vs. Reference
- Solution vs. Product
- M-Architecture vs. T-Architecture
- The \$10000 boolean flag
- Art or Science?
- Science or Art?
- References
- Who is a software architect?
- Modeling
- Capturing the Architecture
- What is modeling?
- Abstraction and Interpretation
- Solving Problems with Models
- Question first, Model second
- Scope of the Model
- What is modeling?
- What is a view?
- How many views?
- Multiple Views
- View Consistency
- Domain and Design Models
- Modeling = Learning
- Domain Model
- Example Domain Model
- Design Model
- Example Design Model (Interfaces)
- Example Design Model (Implementation)
- Some Modeling Notations
- Use Case Scenarios
- Example Music Player Scenarios
- Feature Models
- Feature Model Example
- Feature Model Constraints
- Constrained Feature Model Example
- Feature Configuration
- Use Case Scenarios
- From C4 to C5
- System Context View
- System Context View Example
- Containers View
- Container View Example
- Example Containers
- Components View
- Components View Example
- C4
- Classes View
- C5
- Connectors View
- Connectors View Example
- System Context View
- 4+1
- Logical View
- Logical View Notation
- Example Logical View
- Process View
- Example Process View
- Development View
- Example Development View
- Physical View
- Example Deployment View
- Logical View
- Content is more important than representation
- Model Quality
- Accuracy vs. Precision
- Model Quality - Advice
- Model-Driven Architecture
- References
- Capturing the Architecture
- Modularity and Components
- What is a Software Component?
- Hardware Component
- Software Component
- Examples: Application-specific Components
- Examples: Infrastructure Components
- Black Box
- Recursive Components
- Clustering Components
- Design vs. Run-time
- Distributed Components
- Component Lifecycle Decisions
- Externally Sourced Components
- Discovery
- Selection
- Integration
- Test
- Release
- Deploy
- Stateful Components
- Migration
- Backup and Recovery
- Properties of Components
- Externally Sourced Components
- Component Roles
- Stateless vs. Stateful
- Stateless vs. Stateful Code
- Stateless vs. Stateful Operations
- Components vs. Objects
- Component Technology
- Component Frameworks
- Component Frameworks Demo Videos
- Where to find components?
- Buy vs. Build
- How much does it cost?
- References
- What is a Software Component?
- Reusability and Interfaces
- Interfaces
- Component Interface
- Provided Interface
- Provided Interfacesand Component Roles
- Required Interface
- Explicit Interfaces Principle
- Component Interface
- Information Hiding
- Effective Encapsulation
- Example
- Effective Encapsulation
- Describing Interfaces
- Principle of Least Surprise
- Easy to use?
- Interface Description Languages
- Java/RMI
- C/RPC
- RAML
- OpenAPI/Swagger
- Working With IDL
- API Documentation Demo Videos
- What is an API?
- Is it really API?
- Many Applications
- Developers, Developers, Developers
- Where to find APIs?
- Operating Systems
- Programming Languages
- Hardware Access
- User Interfaces
- Databases
- Web Services
- API Design
- Where is the API?
- API Design: Where to start?
- Who to please?
- Reusable Interfaces
- Usability vs. Reusability
- Easy to reuse?
- Performance vs. Reusability
- Small Interfaces Principle
- How many clients can these APIs satisfy?
- Uniform Access Principle
- Few Interfaces Principle
- Clear Interfaces Principle
- Let's create a new Window
- Expressive? No: Stringly Typed
- Consistent?
- Primitive Operations
- Design Advice
- References
- Interfaces
- Composability and Connectors
- Software Connectors
- Connector: enabler of composition
- Software Connector
- Components vs. Connectors
- Connectors are Abstractions
- Connector Roles and Runtime Qualities
- Connectors and Transparency
- Connector Cardinality
- Connectors and Distribution
- Connectors and Availability
- Software Connector Examples
- RPC: Remote Procedure Call
- File Transfer
- Shared Database
- Message Bus
- Stream
- Linkage
- Shared Memory
- Disruptor
- Tuple Space
- Web
- Blockchain
- References
- Software Connectors
- Compatibility and Coupling
- Compatibility
- Compatible Interfaces
- There's an app adapter for that!
- Adapter
- Wrapper
- Mismatch Example
- Partial Wrappers
- Types of Interface Mismatches
- Synchronous vs. Asynchronous Interfaces
- Half-Sync/Half-Async
- Sync to Async Adapter
- Half-Async/Half-Sync
- Async to Sync Adapter
- How many Adapters?
- Scaling Adapters with N Interfaces
- Composing Adapters
- One or Two Adapters?
- Reusable Adapters and Performance
- How Standards Proliferate
- On Standards
- Standard Software Interfaces
- Representation Formats
- Operations
- Protocols
- Addressing
- Interface Description
- Coupling
- Understanding Coupling
- Coupling Facets
- Session Coupling Examples
- Binding Times
- Be liberal in what you accept, and conservative in what you send.
- Water or Gas Pipe?
- References
- Compatibility
- Deployability, Portability and Containers
- The Age of Continuity
- Deployability Metrics
- Release
- Release Frequency
- Speed vs. Quality
- Software Production Pipeline
- High Quality at High Speed
- Types of Testing
- Types of Release
- Gradual Phase-In
- Essential Continuous Engineering Practices
- Tools
- Build Pipeline Demo Videos
- Container Orchestration Demo Videos
- Virtualization and Containers
- Virtualization
- Lightweight Virtualization with Containers
- VM vs. Container
- Containers inside VMs
- Images and Snapshots
- Virtual Machine Migration
- Inverted Hypervisor
- Virtual Hardware = Software
- References
- The Age of Continuity
- Scalability
- Will it scale?
- Scalability and Workload
- Scalability and Workload: Centralized
- How to scale?
- Scalability and Resources: Decentralized
- Scalability and Resources
- Centralized or Decentralized?
- Scalability at Scale
- Scale Up or Scale Out?
- Scaling Dimensions
- Scalability Patterns
- Directory
- Dependency Injection
- Directory vs. Dependency Injection
- Scatter/Gather
- Master/Worker
- Master Responsibilities
- Worker Responsibilities
- Load Balancing
- Variants
- Sharding
- Computing the Shard Key
- Looking up the Shard Key
- References
- Will it scale?
- Availability and Services
- Components vs. Services
- Business model: how to sell
- Design decisions
- Technology: how to use
- Availability
- Availability Questions
- Monitoring Availability
- Which kind of monitor?
- Availability Incidents
- Downtime Impact
- Contain Failure Impact
- Retry
- Circuit Breaker
- Canary Call
- Redundancy
- State Replication
- Which kind of replication?
- CAP Theorem
- CAP Theorem Proof
- Eventual Consistency
- Event Sourcing
- References
- State Replication
- Components vs. Services
- Flexibility and Microservices
- API Evolution
- Only one chance...
- API Evolution
- API Compatibility
- Semantic Versioning
- Changes and the Build Pipeline
- Version Identifier
- Two in Production
- API Sunrise and Sunset
- To break or not to break
- Who should keep it compatible?
- Layers
- Layering Examples
- Data on the Inside, Data on the Outside
- Tolerant Reader
- Which kind of reader?
- Extensibility
- Extensibility and Plugins
- Microservices
- Monolith vs. Microservices
- Will this component always terminate?
- Will this service run forever?
- Will this microservice continuously change?
- DevOps
- DevOps Requirements
- Feature Toggles
- How small is a Microservice?
- Continuous Evolution
- Hexagon Model
- Decomposition
- Independent DevOps Lifecycle
- Isolated Microservices
- Splitting the Monolith
- Microservice Best Practices
- Bezos's Mandate (2002)
- Evans's Bounded Context (2004)
- Bob Martin's Single Responsibility Principle (2003)
- UNIX Philosophy (1978)
- Separation of Concerns (1974)
- Parnas's Criteria (1971)
- Conway's Law (1968)
- Vogels's Lesson (2006)
- References
- API Evolution
Software Architecture
visual lecture notes
本书目前的完成进度为 100%上次更新时间：2023-02-20
From quality attributes to how to design and model components, interfaces, connectors, containers, all the way to services and microservices.
最低售价
$49.99
$99.99
支付金额
作者利润
PDF
EPUB
434
读者
688
页数
关于
关于本书
These are the revised and illustrated notes of the Software Architecture lecture of the Master in Software and Data Engineering held at the Software Institute at USI Lugano, Switzerland during the Spring of 2023.
The book includes the script for these lectures:
- Introduction
- Quality Attributes
- Definitions
- Modeling Software Architecture
- Modularity and Components
- Reusability and Interfaces
- Composability and Connectors
- Compatibility and Coupling
- Deployability, Portability and Containers
- Scalability
- Availability and Services
- Flexibility and Microservices
捆绑包
本书页包含在这些优惠组合中：
- Pricing
$49.99
最低售价单独购买$109.98建议价格$49.99
- Pricing
$59.99
最低售价单独购买$159.98建议价格$59.99
- Pricing
$49.99
最低售价单独购买$128.99建议价格$55.99
- Pricing
$59.00
最低售价单独购买$128.99建议价格$109
作者
关于作者们
Cesare Pautasso
Cesare Pautasso is full professor at the Software Institute at USI, Lugano, Switzerland. Previously he was a researcher at the IBM Zurich Research Lab. His research group focuses on the Architecture, design and engineering of next-generation Web information systems. He is co-author of "SOA with REST" (2012), "Just Send an Email: Anti-Patterns for Email-Centric Organizations" (2015), the "BPMN Sketch Miner" (2019), "Software Architecture: visual lecture notes" (2020), "Business Process Modeling, Management and Mining: visual lecture notes" (2021), "Beautiful APIs" (2021), "Beautiful API Evolution" (2021), "Beautiful Big APIs" (2022), "RESTful Dictionary" (2022), "Web Atelier: visual lecture notes" (2023), "Patterns for API Design : Simplifying Integration with Loosely Coupled Message Exchanges" (2023), "Unethical Software Engineering: Dark Patterns" (2024).
The Leanpub Podcast
Episode 198
An Interview with Cesare Pautasso
目录
目录
作者的其他著作
作者的其他著作
Leanpub 无条件、零风险的100%满意保证
在支付后的60天内，只需简单点击两下，您便可以退书并且取回先前支付的全部金额。
查看完整条款。
在10美元的购买中赚取8美元，在20美元的购买中赚取16美元
我们在7.99美元或以上的购买中支付80%的版税，在0.99美元到7.98美元之间的购买中支付80%的版税减去0.5美元固定费用。在10美元的销售中您可赚取8美元，在20美元的销售中可赚取16美元。因此，如果我们以20美元的价格售出5000本未退款的图书，您将赚取80,000美元。
（是的，一些作者在Leanpub上已经赚取了远超过这个数额的收入。）
事实上，作者们通过在Leanpub上写作、出版和销售已经赚取了超过1400万美元。
了解更多关于在Leanpub上写作的信息
免费更新。无DRM。
如果你购买了Leanpub的书，只要作者更新这本书，你就可以免费获得更新！许多作者使用Leanpub在他们编写书籍的过程中发布他们的作品。所有读者都可以获得免费更新，无论他们何时购买的书或他们支付了多少钱（包括免费）。
大多数Leanpub书籍都提供PDF（适用于计算机）、EPUB（适用于手机和平板电脑）和MOBI（适用于Kindle）格式。书籍包含的格式会显示在此页面的右上角。
最后，Leanpub的书籍没有任何DRM版权保护的限制，所以你可以轻松地在任何支持的设备上阅读它们。
在 Leanpub 上写作和出版
作者与出版社使用 Leanpub 来出版正在写作中和已完成的书籍，就像这本书一样。你也可以使用 Leanpub 来撰写、出版和销售你的作品！Leanpub 是功能强大的平台，非常适合认真的作者。它结合了简单、优雅的写作与出版流程，以及一个可销售正在写作中的电子书的线上商店。Leanpub 是作家的神奇之笔：只需编写纯文本，然后点击按钮即可出版你的电子书。真的就是这么简单。
学习更多关于在 Leanpub 上写作的信息