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

Understanding service-oriented architecture

In SOA patterns, different application components interact using a communication protocol over the network. Each service provides end-to-end functionality, for example, fetching an order history. SOA is widely adopted by large systems to integrate business processes, for example, taking your payment service from the main application and putting it as a separate solution.

In a general sense, SOAs take monolithic applications and spread some of those operations into individual services that operate independently. The goal of using an SOA is to loosen the coupling of your application’s services. Sometimes, an SOA includes splitting services apart from one another and splitting resources into separate instances of that service. For example, while some choose to store their company’s data in a single database split by tables, an SOA would consider modularizing the application by function into separate databases altogether. This...

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 $15.99/month. Cancel anytime}