Published: 30 August 2018
Analyst(s): Consult the Board Research Team
This summary contains input from ten members on event-driven architecture. We begin this summary by discussing members that have adopted or are planning to adopt event-driven architecture, their existing IT environments based on event-driven architecture, and the ideal breakup of event-driven versus request-driven architecture that they plan to attain after their digital transformation efforts. We then examine members' EDA use cases, the role of event-driven IT, event-design patterns, and EDA tools including message brokers, event-stream analytics platforms, and subscription-enabled data stores. We follow with members' drivers to adopt event-driven architecture and close with an analysis of EDA costs incurred, challenges, and best practices.
©2019 Gartner, Inc. and/or its affiliates.
All rights reserved.
Gartner is a registered trademark of Gartner, Inc. and its affiliates.
This publication may not be reproduced or distributed in any form without Gartner’s prior written permission.
It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact.
While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information.
Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such.
Your access and use of this publication are governed by Gartner’s Usage Policy.
Gartner prides itself on its reputation for independence and objectivity.
Its research is produced independently by its research organization without input or influence from any third party.
For further information, see
Guiding Principles on Independence and Objectivity.