Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Solutions Architect's Handbook - Third Edition

You're reading from  Solutions Architect's Handbook - Third Edition

Product type Book
Published in Mar 2024
Publisher Packt
ISBN-13 9781835084236
Pages 578 pages
Edition 3rd Edition
Languages
Authors (2):
Saurabh Shrivastava Saurabh Shrivastava
Profile icon Saurabh Shrivastava
Neelanjali Srivastav Neelanjali Srivastav
Profile icon Neelanjali Srivastav
View More author details

Table of Contents (20) Chapters

Preface 1. Solutions Architects in Organizations 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

Overcoming architectural constraints

When designing an application architecture, the significant limitations are cost, time, budget, scope, schedule, and resources. Overcoming these constraints is a significant factor that must be considered while designing a solution. You should look at the limitations as challenges that can be overcome rather than obstacles, as challenges always push you to the limit of innovation.

A solutions architect needs to make suitable trade-offs while considering the constraints. For example, a high-performance application results in more cost when you need to add additional caching in multiple layers of architecture. However, sometimes, cost is more important than performance, primarily if a system is used by internal employees, which may not directly impact revenue. Sometimes, the market is more important than launching a fully featured product, and you need to make the trade-off between scope versus speed. In such scenarios, you can take the minimum...

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 €14.99/month. Cancel anytime}