Packt+ | Advance your knowledge in tech

You're reading from Software Architect‚àö¬¢‚Äö√á¬®‚Äö√ë¬¢s Handbook Become a successful software architect by implementing effective architecture concepts

Product type Paperback

Published in Aug 2018

Publisher Packt

ISBN-13 9781788624060

Length 594 pages

Edition 1st Edition

Concepts

Software Architecture

Author (1):

Joseph Ingeno

View More author details

Table of Contents (24) Chapters

Title Page

Dedication

Packt Upsell

Contributors

Preface

1. The Meaning of Software Architecture FREE CHAPTER

2. Software Architecture in an Organization

3. Understanding the Domain

4. Software Quality Attributes

5. Designing Software Architectures

6. Software Development Principles and Practices

7. Software Architecture Patterns

8. Architecting Modern Applications

9. Cross-Cutting Concerns

10. Performance Considerations

11. Security Considerations

12. Documenting and Reviewing Software Architectures

13. DevOps and Software Architecture

14. Architecting Legacy Applications

15. The Soft Skills of Software Architects

16. Evolutionary Architecture

17. Becoming a Better Software Architect

1. Other Books You May Enjoy

Leave a review - let other readers know what you think

Index

Integrating with legacy applications

Software architects may need to integrate a legacy application with another software application. If you are responsible for the legacy application, refactoring it may be necessary in order to modernize it to the point that it can be integrated with newer applications.

When integrating a legacy application with another application, some considerations should be made by the software architect.

Confirming the need for integration

Prior to expending the effort to integrate with a legacy application, thought should be given to ensure that the integration is necessary. Depending on the situation, it may be easier to migrate the functionality that is needed from the legacy application rather than move forward with integration.

When deciding to migrate or integrate, consider the amount of functionality that is needed from the legacy system and the complexity of that functionality. If there is a large amount of functionality and/or the functionality is highly complex...