Gartner Blog Network


Event Thinking: a Challenge And an Imperative

by Yefim Natis  |  September 12, 2017  |  Comments Off on Event Thinking: a Challenge And an Imperative

The challenge of event thinking is that the IT designer must accept uncertainty. In transactional systems the callers request is guaranteed to be fulfilled or the caller will be told of a failure. In event-driven systems the source cannot be certain that their intent (if any) will be fulfilled: the event handler has full control of the reaction to the notification and may or may not do what the source expects. This uncertainty is 1. Completely contrary to 50 years of IT focused on guaranteed integrity of action and 2. is a better model of real life where all agreements have some degree of the leap of faith. The first, at the core, is why it is so hard for event thinking to take hold. The second is why the digital business success demands it.

Read Innovation Insight for Event Thinking for more Gartner guidance on event thinking.

Read Gartner on Event Processing in Digital Business: Recent Research for more Gartner guidance on #EventDriven.

Category: 

Tags: aws  cio  cloud  event-processing  events  iot  it-architect  microevents  microservices  paas  

Yefim V. Natis
VP Distinguished Analyst
17 years at Gartner
33 years IT industry

Yefim Natis is a vice president and Gartner distinguished analyst in Gartner Research. Mr. Natis' research focuses on enterprise software infrastructure, including technologies such as application servers, cloud application platforms… Read Full Bio




Comments are closed

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.