Gartner defines an event-driven architecture (EDA) as a design paradigm in which a software component executes in response to receiving one or more event notifications. EDA is more loosely coupled than the client/server paradigm because the component that sends the notification doesn’t know the identity of the receiving components at the time of compiling.Adoption of EDA in Asia Pacific remains uneven with markets like Hong Kong and Australia in line with more developed markets like the US. Yet, even advanced markets like Korea and Japan have yet to accept the design paradigm.In this PodChats for FutureCIO, we speak to Phil Scanlon, vice president of field technology, APJ & ME with Solace to get his perspective on what EDA truly means to a business and the starting point of an EDA journey.1. What is your definition of EDA?2. What is the state of EDA adoption in Asia Pacific compared to the rest of the world?3. For decades enterprises have relied on information systems such as ERP to give them up-to-date data about the business. Do they understand the difference between what applications like ERP bring compared to EDA?4. For businesses that have not reached a state of EDA maturity, what are some of the obstacles that lie in their way? 5. Which are the business roles that appreciate EDA the most and which needs more education?6. Any misconceptions particularly business leaders that become barrier to EDA acceptance?7. Who should lead EDA adoption across the enterprise?8. How do APAC organisations balance the costs and benefits of EDA?9. How prepared are organisations to support real-time data distribution?a. Given that EDA is an acceleration of data in the decision-making process, how does IT ensure security policies and frameworks remain in place even with EDA in place?10. Coming into 2022, what do you see will further drive EDA adoption in APAC?

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related