Senate hearing on the modernization program of the air traffic control system, which has taken more than 15 years and consumed many billions of dollars. Witnesses: Senators Richard H. Bryan, Wendel H. Ford, Slade Gorton, and John McCain; Phil Boyer, pres., Aircraft Owner's and Pilots Assoc. (AOPA) Legislative Action; Gerald L. Dillingham, Ph.D., Associate Director, Transportation Issues, Resources, Community, and Economic Development Div., General Accounting Office; Jane Garvey, Administrator, Federal Aviation Administration (FAA); and Margaret T. Jenny, director, airline business and operations analysis, U.S. Airways.

Long path to better systems that last longer and make engineers and customers happier KEY FEATURES ● Guidance, trade-offs analysis, principles, and insights on understanding complex microservices and monoliths problems and solutions at scale. ● In-depth coverage of anti-patterns, allowing the reader to avoid pitfalls and understand how to handle architecture at scale better. ● Concepts and lessons learned through experience in performing code and data migration at scale with complex architectures. Best usage of new technology using the right architecture principles. DESCRIPTION This book is a comprehensive guide to designing scalable and maintainable software written by an expert. It covers the principles, patterns, anti-patterns, trade-offs, and concepts that software developers and architects need to understand to design software that is both scalable and maintainable. The book begins by introducing the concept of monoliths and discussing the challenges associated with scaling and maintaining them. It then covers several anti-patterns that can lead to these challenges, such as lack of isolation and internal shared libraries. The next section of the book focuses on the principles of good software design, such as loose coupling and encapsulation. It also covers several software architecture patterns that can be used to design scalable and maintainable monoliths, such as the layered architecture pattern and the microservices pattern. The final section of the book guides how to migrate monoliths to distributed systems. It also covers how to test and deploy distributed systems effectively. WHAT YOU WILL LEARN ● Understand the challenges of monoliths and the common anti-patterns that lead to them. ● Learn the principles of good software design, such as loose coupling and encapsulation. ● Discover software architecture patterns that can be used to design scalable and maintainable monoliths. ● Get guidance on how to migrate monoliths to distributed systems. ● Learn how to test and deploy distributed systems effectively. WHO THIS BOOK IS FOR This book is for software developers, architects, system architects, DevOps engineers, site reliability engineers, and anyone who wants to learn about the principles and practices of modernizing software architectures. The book is especially relevant for those who are working with legacy systems or want to design new systems that are scalable, resilient, and maintainable. TABLE OF CONTENTS 1. What’s Wrong with Monoliths? 2. Anti-Patterns: Lack of Isolation 3. Anti-Patterns: Distributed Monoliths 4. Anti-Patterns: Internal Shared Libraries 5. Assessments 6. Principles of Proper Services 7. Proper Service Testing 8. Embracing New Technology 9. Code Migrations 10. Data Migrations 11. Epilogue

In 1981, the FAA began a program to modernize the air traffic control (ATC) system by replacing aging equipment & accommodating predicted growth in air traffic. It has had difficulty for more than two decades in meeting cost, schedule, & performance targets. The performance-based Air Traffic Org. (ATO) was created in 2004 to improve the management of the modernization effort. In Oct. 2004, a panel discussed the factors that have affected FAA's ability to acquire new ATC systems. They identified steps that FAA's ATO could take in the short term to address these factors, as well as longer term steps that could be taken to improve the modernization program's chances of success & help the ATO achieve its mission.