Search icon CANCEL
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
Architectural Patterns

You're reading from   Architectural Patterns Uncover essential patterns in the most indispensable realm of enterprise architecture

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781787287495
Length 468 pages
Edition 1st Edition
Arrow right icon
Authors (4):
Arrow left icon
Pethuru Raj Chelliah Pethuru Raj Chelliah
Author Profile Icon Pethuru Raj Chelliah
Pethuru Raj Chelliah
Harihara Subramanian J Harihara Subramanian J
Author Profile Icon Harihara Subramanian J
Harihara Subramanian J
Pethuru Raj Pethuru Raj
Author Profile Icon Pethuru Raj
Pethuru Raj
Anupama Murali Anupama Murali
Author Profile Icon Anupama Murali
Anupama Murali
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Demystifying Software Architecture Patterns FREE CHAPTER 2. Client/Server Multi-Tier Architectural Patterns 3. Object-Oriented Software Engineering Patterns 4. Enterprise Integration Patterns 5. Domain-Driven Design (DDD) Principles and Patterns 6. Enterprise Architecture Platforms and Tools 7. Service-Oriented Architecture (SOA) 8. Event-Driven Architectural Patterns 9. Microservices Architecture Patterns 10. Patterns for Containerized and Reliable Applications 11. Software-Defined Clouds - the Architecture and Design Patterns 12. Big Data Architecture and Design Patterns

Improving the performance of EDA-based processes/systems

In the case of persisting events, all events that are pushed to the event queue are persisted to the event log. This makes the system slow. In order to improve the performance of the system, there should be a mechanism to persist only events that have the capability to alter the state of the system, that is, read events do not alter the state of the system whereas write events will alter the state. So, there should be a mechanism in place to persist only write events.

This can be made possible with the event collectors by differentiating read events and write events. There should also be separate queues to handle read and write events. Using this mechanism, it is easy to ensure that events in the read event queue are not persisted and only the events in the write event queue are persisted. This concept is depicted in the...

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