
IDC PeerScape: Practices for Implementing Event Brokers in Event-Driven Architecture
Description
IDC PeerScape: Practices for Implementing Event Brokers in Event-Driven Architecture
This IDC PeerScape outlines three practices to increase the effectiveness of implementing event brokers when moving toward an event-driven architecture. They include: Leverage vendor expertise and available training as needed to increase existing skill sets and build organizational awareness when getting started to build ongoing support. Map use case requirements and message attributes to vendor pricing models can reduce costs and improve potential ROI. Utilize an event broker to separate queuing from an iPaaS, limiting the overall workload while utilizing asynchronous messaging middleware for queue data and data traffic."Event brokers are a critical technology to flowing real-time data through the organization in event-driven architectures, but there is a large variation in the types of brokers an organization might need to support a given use case. Selecting the right one might mean selecting more than one depending on the use case and message patterns," says Shari Lava, research director, AI and Automation at IDC.
Please Note: Extended description available upon request.
Table of Contents
5 Pages
- IDC PeerScape Figure
- Executive Summary
- Peer Insights
- Practice 1: Leverage Vendor Expertise/Training to Build Skill Sets and Organizational Awareness for Ongoing Support
- Challenge
- Example
- Guidance
- Practice 2: Map Message Pattern Requirements to Vendor Pricing Models to Optimize Costs and Accelerate ROI
- Challenge
- Example
- Guidance
- Practice 3: Use Event Brokers to Split Queuing from iPaaS to Manage Workload and Data Traffic Asynchronously
- Challenge
- Example
- Guidance
Pricing
Currency Rates
Questions or Comments?
Our team has the ability to search within reports to verify it suits your needs. We can also help maximize your budget by finding sections of reports you can purchase.