Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Software Architect‚àö¬¢‚Äö√ᬮ‚Äö√묢s Handbook
  • Toc
  • feedback
Software Architect’s Handbook

Software Architect’s Handbook

By : Joseph Ingeno
4.4 (10)
close
Software Architect’s Handbook

Software Architect’s Handbook

4.4 (10)
By: Joseph Ingeno

Overview of this book

The Software Architect’s Handbook is a comprehensive guide to help developers, architects, and senior programmers advance their career in the software architecture domain. This book takes you through all the important concepts, right from design principles to different considerations at various stages of your career in software architecture. The book begins by covering the fundamentals, benefits, and purpose of software architecture. You will discover how software architecture relates to an organization, followed by identifying its significant quality attributes. Once you have covered the basics, you will explore design patterns, best practices, and paradigms for efficient software development. The book discusses which factors you need to consider for performance and security enhancements. You will learn to write documentation for your architectures and make appropriate decisions when considering DevOps. In addition to this, you will explore how to design legacy applications before understanding how to create software architectures that evolve as the market, business requirements, frameworks, tools, and best practices change over time. By the end of this book, you will not only have studied software architecture concepts but also built the soft skills necessary to grow in this field.
Table of Contents (19 chapters)
close
close
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
Free Chapter
1
The Meaning of Software Architecture
The Meaning of Software Architecture
What is software architecture?
Why is software architecture important?
Who are the consumers of software architectures?
What is the software architect role?
Summary
2
Software Architecture in an Organization
Software Architecture in an Organization
Types of software architects
Software development methodologies
Project management
Office politics
Software risk management
Configuration management
Software product lines
Summary
3
Understanding the Domain
chevron up
Understanding the Domain
Developing business acumen
Domain-driven design
Requirements engineering
Requirements elicitation
Summary
4
Software Quality Attributes
Software Quality Attributes
Quality attributes
Maintainability
Usability
Availability
Portability
Interoperability
Testability
Summary
5
Designing Software Architectures
Designing Software Architectures
Software architecture design
The importance of software architecture design
Top-down versus bottom-up design approaches
Greenfield versus brownfield software systems
Architectural drivers
Leveraging design principles and existing solutions
Documenting the software architecture design
Using a systematic approach to software architecture design
Attribute-driven design (ADD)
Microsoft's technique for architecture and design
Architecture-centric design method (ACDM)
Architecture development method (ADM)
Tracking the progress of the software architecture's design
Summary
6
Software Development Principles and Practices
Software Development Principles and Practices
Designing orthogonal software systems
Minimizing complexity
Following SOLID design principles
Helping your team succeed
Summary
7
Software Architecture Patterns
Software Architecture Patterns
Software architecture patterns
Layered architecture
Event-driven architecture
The Model-View-Controller pattern
The Model-View-Presenter pattern
The Model-View-ViewModel pattern
The Command Query Responsibility Segregation pattern
Service-oriented architecture
Summary
8
Architecting Modern Applications
Architecting Modern Applications
Monolithic architecture
Microservice architecture
Serverless architecture
Cloud-native applications
Summary
9
Cross-Cutting Concerns
Cross-Cutting Concerns
Cross-cutting concerns
General guidelines for cross-cutting concerns
Implementing cross-cutting concerns
Aspect-oriented programming
Types of cross-cutting concerns
Cross-cutting concerns for microservices
Summary
10
Performance Considerations
Performance Considerations
The importance of performance
Defining performance terminology
Taking a systematic approach to performance improvement
Server-side caching
Improving web application performance
Database performance
Summary
11
Security Considerations
Security Considerations
Securing software systems
Threat modeling
Secure by design
Cryptography
Identity and access management (IAM)
Most common web application security risks
Summary
12
Documenting and Reviewing Software Architectures
Documenting and Reviewing Software Architectures
Uses of software architecture documentation
Creating architecture descriptions (ADs)
Reviewing software architectures
Summary
13
DevOps and Software Architecture
DevOps and Software Architecture
DevOps
DevOps toolchain
DevOps practices
Architecting for DevOps
Deploying to the cloud
Summary
14
Architecting Legacy Applications
Architecting Legacy Applications
Legacy applications
Refactoring legacy applications
Migrating to the cloud
Moving to an agile approach
Modernizing build and deployment processes
Integrating with legacy applications
Summary
15
The Soft Skills of Software Architects
The Soft Skills of Software Architects
Soft skills
Communication
Leadership
Negotiation
Working with remote resources
Summary
16
Evolutionary Architecture
Evolutionary Architecture
Change is inevitable
Lehman's laws of software evolution
Designing evolutionary architectures
Summary
17
Becoming a Better Software Architect
Becoming a Better Software Architect
Practicing continuous learning
Participating in open source projects
Writing your own blog
Spending time teaching others
Trying new technologies
Continuing to write code
Attending user groups and conferences
Taking responsibility for your work
Attending to your well-being
Summary
18
Other Books You May Enjoy
Other Books You May Enjoy
Leave a review - let other readers know what you think

Domain-driven design

Understanding the domain of your software application is part of what is necessary to discover the appropriate architecture for any solutions you need to develop. The domain is the subject and body of knowledge on which the software will be applied.

The term domain-driven design (DDD) was coined by Eric Evans in his book, Domain-Driven Design: Tackling Complexity in the Heart of Software. DDD is an approach to developing software that aims to make the software better by focusing on the domain. It has a set of concepts and patterns that have successfully been used to solve problems and build great software.

DDD is particularly useful for large software applications that have complex and sizable models. DDD helps you to solve complex problems. Even if you decide not to follow DDD fully while architecting your applications, some DDD concepts may be helpful to...

End of Section 3
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete