Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Solutions Architect's Handbook

You're reading from   Solutions Architect's Handbook Kick-start your career with architecture design principles, strategies, and generative AI techniques

Arrow left icon
Product type Paperback
Published in Mar 2024
Publisher Packt
ISBN-13 9781835084236
Length 578 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Neelanjali Srivastav Neelanjali Srivastav
Author Profile Icon Neelanjali Srivastav
Neelanjali Srivastav
Saurabh Shrivastava Saurabh Shrivastava
Author Profile Icon Saurabh Shrivastava
Saurabh Shrivastava
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Solutions Architects in Organizations FREE CHAPTER 2. Principles of Solution Architecture Design 3. Cloud Migration and Cloud Architecture Design 4. Solution Architecture Design Patterns 5. Cloud-Native Architecture Design Patterns 6. Performance Considerations 7. Security Considerations 8. Architectural Reliability Considerations 9. Operational Excellence Considerations 10. Cost Considerations 11. DevOps and Solution Architecture Framework 12. Data Engineering for Solution Architecture 13. Machine Learning Architecture 14. Generative AI Architecture 15. Rearchitecting Legacy Systems 16. Solution Architecture Document 17. Learning Soft Skills to Become a Better Solutions Architect 18. Other Books You May Enjoy
19. Index

Defining a strategy for system modernization

Often, a legacy system gets left out of an enterprise’s overall digital strategy, and issues get addressed as needed. A reactive approach prevents organizations from executing overall system modernization and benefits.

If your legacy system has serious business challenges, such as security and compliance issues, or cannot address a business need, you can take a big-bang approach. In the big-bang method, you build a new system from scratch and shut down the old system. This approach is risky but addresses a business need that can be mitigated from the existing legacy system.

The other approach is a phased approach, where you upgrade one module at a time and keep running both the old and the new systems. A phased approach is less risky but takes a long time and may be more expensive, as you need to maintain both environments with increased network and infrastructure bandwidth.

Approaching your application portfolio, prioritizing...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image