Hacker News new | ask | show | jobs
by BenoitP 1807 days ago
The long term trend for data access is having a reactive component; stream processing engines allow you do have that.

On the other hand databases have a huge lock-in power (been trying to strangle an Oracle myself for over 5 years now). It is lucrative to be in the database business.

I'd say that every project with a claim of some improvement can, and should try to establish itself in the market; and that having it join the Apache foundation is a great way to get some brand recognition on the cheap.

----

Also, Heron is not that new. It has been developed at Twitter, for replacing Storm IIRC.
1 comments
skywhopper 1807 days ago
But none of them spell out for what use cases they excel over the other options. Since they are all under the ASF banner, it’s impossible to know which is “better” for me. They are all just “great stream processing engines”. But surely they must have diverging properties for given use cases. But none of the pages even attempt to say how they differ. Just “try it out!!”
link
mumblemumble 1807 days ago
Years ago, I found a scientific paper that evaluated them all on a fairly detailed rubric. As I recall, it turned out that they're all, in actual fact, crap stream processing engines. You just need to pick the one that's crap at things you don't need to do.

(I could frame it in a more glass half full way, but I find that the pessimistic way of looking at it helps a lot with trimming down options when you have far, far, far too many options.)

link
brandmeyer 1807 days ago
Citation needed. And not in the snarky way - I'd really like to read that paper :)
link
fizwhiz 1807 days ago
I'm guessing they were referring to "Scalability! But at what COST?"

https://www.usenix.org/system/files/conference/hotos15/hotos...

link
mumblemumble 1807 days ago
I've long since lost track of it. It would be 5 or 6 years out of date at this point, anyway, so probably not very useful for informing decisions anymore.
link
monocasa 1807 days ago
I've just accepted that mindset as a part of the art of engineering. Shifting the inherent crappiness of a domain around to where it doesn't matter as much for your use case.
link