Back to the Blog
Well, after a long period of working on a number of operational projects, I’m going to take a break from writing code and actually do some blogging again. For some this is good news (and I quote from a private note):
I’m thankful you’ve started blogging again. For a while there I was afraid you’d stopped blogging because of the attacks from Opher and those who side with him.
And for others this is bad news (and I quote from a passionate public comment):
Oh please Tim! After several months of quiet on this front, do we really need to start going around these loops again?
I fully expect to be either (1) relentlessly attacked or (2) completely ignored. Either is perfectly OK with me because after a long absence, I realize that it is our professional and ethical responsibility to debunk the claims of all these “instant coffee” experts in complex event processing.
The “event process vocal minority” is full of well-intended, but inexperienced folks who have never (or rarely) worked in an operational data center where they had to deal with anything complex and have never written a line of code to detect an outage or a security threat before it caused damage. It is full of people who want to sell us their “can do all, save the planet” software and silence those who disagree.
Sadly, the event processing and CEP fields are dominated by academics, marketing people and paid analysts who are constantly releasing self-serving press releases where they claim to the world they are doing something “new” or “special”. Truth in fact (no conflict of interest here), most of this software is semi-useless for detecting anything remotely “complex” and is simply an GUI-based IDE around some relatively simple query or rule processing code. In practice, we can do more to “detect” things with free and open Perl or PHP code. Really. I am not kidding.
It has been many years since the software marketing folks got a hold of the term “CEP”. They hijacked it from it’s innocent genesis in network security and complex fault management (as funded by DARPA to help make the US a safer place), and turned it into a metaphor for processing transaction streams (mostly related to financial services).
This time, I am going to “take off the gloves” because I am really disappointed in the boring “attacks by “professionals” those who only talk-the-walk or sell to FSI. The attacks, censorship and “false hero worship” in the event processing space is so self-serving and is based on greed and ego-gratification. Folks do not even reference the prior art in the field! They are “pioneers” as if their first visit to Hawaii makes them the one founding fathers there as well, LOL.
In the past 6 months I have have fought cyberattacks from “those countries” attackers; written, tested and implemented security event countermeasures; put together CDNs and virtual fault management services; worked in the clouds on performance management projects; modified, installed and tested PHP detection code; worked on machine language translation projects, and more.
I don’t have anything to sell you. I don’t want you to buy my “CEP engine” and I don’t want you to hire me or sponsor this blog. I don’t want a penny from you. I am “dangerous” because I only want you to know the truth, from a long time technology person who has working in IT operations for nearly 20 years and actually needs to detect complex events and situations.