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 solutions architect career by learning architecture design principles and strategies

Arrow left icon
Product type Paperback
Published in Mar 2020
Publisher Packt
ISBN-13 9781838645649
Length 490 pages
Edition 1st Edition
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 (18) Chapters Close

Preface 1. The Meaning of Solution Architecture 2. Solution Architects in an Organization FREE CHAPTER 3. Attributes of the Solution Architecture 4. Principles of Solution Architecture Design 5. Cloud Migration and Hybrid Cloud Architecture Design 6. Solution Architecture Design Patterns 7. Performance Considerations 8. Security Considerations 9. Architectural Reliability Considerations 10. Operational Excellence Considerations 11. Cost Considerations 12. DevOps and Solution Architecture Framework 13. Data Engineering and Machine Learning 14. Architecting Legacy Systems 15. Solution Architecture Document 16. Learning Soft Skills to Become a Better Solution Architect 17. Other Books You May Enjoy

Incompatibility with other systems

In addition to end users, every system needs to integrate with other IT systems. Those systems may be a part of different departments, clients, partners, or suppliers. The various systems need to exchange data in a standard format that evolves over time. Almost every few years, files and data format standards get changed to increase data exchange efficiency, and most systems require changes to adopt these. Hard-to-change legacy systems that stick to using an old format could result in system incompatibility and a system that your supplier and partner may not want to use. The inability to accommodate standard needs adds greater risk to businesses due to complex workarounds and lost productivity.

Adding a workaround for simple business needs may make a system more complex. Modern systems are built on a service-oriented architecture, which makes it easier to accommodate any new requirement by adding a new service independently. Old systems are often built...

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