Book Image

Software Architect's Handbook

By : Joseph Ingeno
Book Image

Software Architect's Handbook

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)

Refactoring legacy applications

When you begin working on a legacy application, you will want to refactor it in order to make it more maintainable. You may need to implement new features, fix defects, improve the design, increase quality, or optimize the application. In order to perform these types of task, the legacy system must be in a state where changes can easily be made and without much risk.

In the classic book Refactoring: Improving the Design of Existing Code, author Martin Fowler defines refactoring as …the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure. Any refactoring that is performed should safely improve the code in some way, without affecting the business logic and expected functionality.

Before making any changes, it is helpful to have the right attitude when...