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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Software Architect’s Handbook

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

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781788624060
Length 594 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Joseph Ingeno Joseph Ingeno
Author Profile Icon Joseph Ingeno
Joseph Ingeno
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

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 18. Other Books You May Enjoy

Event-driven architecture

An event is the occurrence of something deemed significant in a software application, such as a state change, that may be of interest to other applications or other components within the same application. An example of an event is the placement of a purchase order or the posting of a letter grade for a course that a student is taking.

An event-driven architecture (EDA) is a distributed, asynchronous software architecture pattern that integrates applications and components through the production and handling of events. By tracking events, we don't miss anything of significance related to the business domain.

EDAs are loosely coupled. The producer of an event does not have any knowledge regarding the event subscribers or what actions may take place as a result of the event.

SOA can complement EDA because service operations can be called based on events...

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