As we've described in this CONQUER series (Part 1, Part 3), distributed systems are information tools enabling volitional entities in relationships of permission and obligation to achieve their intents via purposeful dialogs, communicated among software components proxying their wills, consisting of imperative, declarative, and interrogative sentences: commands, queries, and events. Let's briefly consider the nature … Continue reading CONQUER Part 4: Software Morality
Tag: events
At Any Event, or at Every Event?
Still on the trail of conceptual clarity around events. In the last post in this - this is the third, so let's say 'series' - we discussed the difference in knowledge and data. I used the familiar-to-most query against a relational database to illustrate the difference. Let's return to that example for a moment. The … Continue reading At Any Event, or at Every Event?
The Event Re-Renaissance Continued: Knowledge vs. Data
In my last post, we started digging into the re-emergence of complex event processing and event-driven architectures which has been enabled by the latest generation of stateful stream processors such as Spark Streaming, Samza, Kafka Streams, Apache Flink, and Google DataFlow. Today let's start to develop a clear line of sight into the underlying conceptual … Continue reading The Event Re-Renaissance Continued: Knowledge vs. Data
The Event Renaissance is Reborn Event
We are plumbing our event-driven architecture here at Cambia, and, as we were socializing our approach internally, a question came up about how the stateful-streaming-based complex event processor we're rolling out will fit into the overall flow of data. As I struggled to answer it clearly, I realized that the layers of event-related technology that … Continue reading The Event Renaissance is Reborn Event
Health IT Architect 