Components of Event-driven SOA

Components of Event-driven SOA

What are all the components of service oriented architecture SOA and EDA, and how can they be used together in one architecture?

Services: DNA of SOA
The most easily understood component of service oriented architecture SOA is services. These are software modules that represent reusable business functionality, like “process order” or “bill customer.” There are also system services, like auditing, logging, and even orchestration.

SOA service oriented architecture is fundamentally heterogeneous, which basically means companies host services on many different platforms. The majority of companies have Java, Java EE, and .NET-based services. Most companies also service enable existing applications, exposing functionality as services using adapters or web services.

Events: DNA of EDA
A business event is any activity that happens inside or outside your business. If you’re lucky, an event is captured somewhere in your software infrastructure either directly or indirectly.

There are thousands to millions of events that occur in most companies on a daily basis. All events somehow get noted and affect the operations of a company. Most events will not be relevant, some will have a negative impact on a business, others will have a positive impact, and a few will offer a big opportunity.

All companies are event driven, since our world is event driven. However, most IT applications and processes are geared toward predictable, repeatable events. It’s when events happen that are notable or exceptional that most businesses have trouble. Most companies also find it hard to fit an event into a larger trend that may affect their business.