• Blog
  • About
  • Archives

elemental links

brenda michelson's technology advisory practice

Absence of Event = Event

July 14, 2011 By brenda michelson

In this week’s Active Information post, I riff off a quote by Jud Valeski the CEO of Gnip, on the dearth of event-driven talent:

“Beyond infrastructure issues, as engineers, the web app programming we’ve been doing over the past 15 years has taught us to build applications in a highly synchronous transactional manner…”

“…You would be shocked at the ratio of engineers who can’t build event-driven, asynchronous data processing applications, to those who can, yet this is a big part of this space.”

If you are a frequent reader here, you’ve seen the event constructs I published over there.

One that I didn’t include is the fact that the absence of an event can be an event.  Chris Martins brought that up on Twitter.

In my initial event writing, I wrote of a system heartbeat example:

“…a business-to-business order gateway is supposed to be emitting System Heartbeat events every 15 minutes. The System Heartbeat events inform IT operations the gateway is up and running. The absence of a heartbeat event indicates a failure. If the order gateway is down, business customers are likely to place an order with a competitor.”

On Twitter yesterday, I mentioned an event-driven billing subsystem I’m currently working on.  In that system, we’ll be generating a (standard) projected monthly invoice.  The invoice generation starts when the party is approved for billing.

Invoice regeneration is triggered by a set of events, including a change in plan, the receipt of a payment, or the absence of the receipt of payment.  In this subsystem, the absence of a receipt is a non-payment event.

So, yes.  The absence of an event is absolutely an event.

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to email this to a friend (Opens in new window)

Filed Under: active information, event driven architecture, event processing Tagged With: #hpio

Brenda M. Michelson

Brenda Michelson

Technology Architect.

Trusted Advisor.

(BIO)

  • Email
  • LinkedIn
  • RSS
  • Twitter

Recent Posts

  • Experts Sketch
  • PEW Research: Tech Saturation, Well-Being and (my) Remedies
  • technology knowledge premise
  • The Curse of Knowledge
  • better problems and technology knowledge transfer

Recent Tweets

  • Harshest editorial feedback I ever received “stultified and like death”… (wildly popular paper, as it turned out):… https://t.co/qWNwBCOS5i February 28, 2023 2:16 pm
  • “…where the process of drawing itself can take us. We can follow a suggestion, a squiggle, shadow, or smudge, and s… https://t.co/oRg0x2LoXG November 30, 2022 5:05 pm
  • On the waiting list for Post, join me (on the waitlist) via https://t.co/U8wYK707f6 November 24, 2022 4:17 pm
© 2004-2022 Elemental Links, Inc.
loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.