BCA unifies SOA and EDA by moving the focus of architectural design from access methods (request/reply, event-management), middleware and development tools to the notion of software modularity. The architecture of software modularity is primary, and designers that focus on creating business components that map well to business functions and which have the proper interfaces or event-descriptors see SOA and EDA as complementary. Business components can have either client-driven or event-driven interfaces, making SOA and EDA both manifestations of BCA.

Figure 1 : Business Component Architecture - Unifying SOA & EDA

Benefits of Business Components
Business Component Applications are assembled by combining a set of reusable Business Components. BCA makes systems easier to understand and manage by business analysts, in contrast to technical component architecture (such can COM, CORBA or RPC), which makes systems easier to understand and change by technical programmers. BCA is thus a software architecture where individual modules have business-level semantics and technical-level encapsulation, in which individual Business Components communicate either via call-based interfaces (SOA), or via messages and events (EDA), making the overall system easier to manage, modify and change without programmer intervention.

Learn more:

 The Mission of Application Integration

 Streamlining your Integration Strategy

 Business Component Architecture: Unifying SOA and EDA