Streaming data contains events that are updates to the states of data sources. When choosing an architecture to process it, the role of an event broker, like Apache Kafka or …
Read Story
Streaming events are updates about the states of things: applications, devices & infrastructure. When choosing an architecture to process them, the role of an event broker, like Apache Kafka or …
Read Story
I bet you think this is about the rise of Netflix, YouTube, Disney+ etc. It isn’t. Sure, streaming video has eclipsed TV, but that's old news. I’m referring to the …
Read Story
For a growing class of business-critical applications, what’s in an application database is likely to be out of sync with the real world - insights are computed too late to …
Read Story
“Edge AI” is no more of a market than “Edge Linear Regression”. AI at the network edge (or anywhere else) is useless unless it’s applied to a specific problem, which …
Read Story
Brokers don’t run applications - they just act as a buffer between the real world and an application that analyzes them. An event stream processor (in Apache Kafka/Pulsar terms) or …
Read Story
Organizations are drowning in streams of data and it's only going to get worse. Sure, lots of it can be stored, but most of it is only fleetingly useful Traditional …
Read Story
Event Streams are the Future of Big Data (Tune in to my presentation to the Apache Kafka EU Summit on Wednesday 12 May, to learn how to build a Swim …
Read Story
It’s a catchy phrase, I guess, for the twitterati. But apart from the obvious - there's lots of oil and we're drowning in data - the image tells you everything …
Read Story
Like (Apache 2.0 licensed) Swim, Apache Flink is a distributed processing engine for stateful computation on unbounded and bounded data streams. Both run distributed applications using clustered resources, and perform …
Read Story