Architectural Patterns by Pethuru Raj

Author:Pethuru Raj
Language: eng
Format: epub
Tags: COM091000 - COMPUTERS / Cloud Computing *, COM011000 - COMPUTERS / Systems Architecture / General, COM048000 - COMPUTERS / Systems Architecture / Distributed Systems and Computing
Publisher: Packt
Published: 2017-12-22T08:22:50+00:00

Service-oriented architecture and event-driven architecture (SOA versus EDA)

Organizations across the world are changing their structures rapidly and are moving toward on-demand business models. There is an increase in the movement toward setting up network-oriented business structures that will have autonomous service providers and consumers. Outsourcing is also very prominent as many parts of the business process will also be outsourced to external business partners. Various departments and business units who are present within organizations are taking on the role of service providers. The focus of these service providers is to increasingly provide services to the external market entities. This necessitates organizations being agile enough to quickly respond to changes or events that happen in the external environment. All these aspects demand a paradigm shift from a command-driven, tightly coupled, service-driven SOA concept to a more loosely coupled model that is driven by events. EDA is a publish/subscribe type of pattern. In the context of EDA, the publisher is completely unaware of the subscriber, and vice versa. Components of the EDA pattern are so loosely coupled that only the semantics of the message is shared between them. Now, the decision that needs to be made is when to use SOA and when to use EDA.

There is a common tendency to use EDA and SOA interchangeably because of the nature of their working. But that should not be the case. There are clear differentiators between the two architectural options. For situations that demand a strong cohesion in the business processes, SOA is the ideal choice of architecture. The following are the various scenarios in which a command/control style of SOA could be an ideal choice of architecture for organizations:

If there exists a vertical interaction between the various hierarchical layers of functions that exist in an organization

If there are functional request-and-reply processes such as man-machine dialogues where the user feeds a question and waits for an answer

If there are processes that are transactional in nature that requires commit and rollback features

If data enrichment is required in a message for it to be published to its full content in a formal format

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.