31–40 of 62 posts
https://github.com/s4/examples/blob/master/twittertopiccount...
Im too dim to figure out why it would be done this way (besides the fact thats its an early proof of concept demo). Any idea?
S4 is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous unbounded streams of data. I'm sure this is cool and useful technology. At this moment, from the marketing-speak, I have no idea what it does except that it has something to do with volumes of streaming data. Whose data? Is it a service? (Maybe n…
My attempt at a more friendly description of S4 (based on my very limited understanding of it - please correct me if I'm wrong): When processing large amounts of streaming data, you have to process the data as fast as it comes in or else you can't keep up. You probably wonder: "Why not simply delay the processing of new data while the old data is being processed?". The problem lies in the fact we're dealing with a st…
It sounds like a slightly more structured and distributed Unix shell pipeline; but from looking at the twitter example, a lot more awkward to use, owing to being structured around Java. I imagine a composition language (DSL) wrapped around it could improve its usability - especially ad-hoc experimentation - greatly; at least one better than Spring IoC xml.
If you want to stick with the JVM, have you considered using Scala and the cake pattern?
http://jonasboner.com/2008/10/06/real-world-scala-dependency...
If you want to stick with Java and want to use IoC without the hell that is Spring, I suggest Guice (which consists of a smaller, cleaner core and uses annotations and DSLs in place of XML):
Earlier quoted context omitted.
It's not marketing speak, it's research speak. I have worked on a similar project (and will work on it again in the future), and I know exactly what they mean by those things. General purpose: in the same way C is a "general purpose" language. It can handle arbitrary problems. Distributed: designed to be used across multiple compute nodes. Scalable: they've made the effort to ensure that performances increases as the…
No, I think what sabat is saying is that the front page documentation is geared towards the wrong audience and needs to have less general information on usage. I think if the following actually had examples of use, I'd try it out: http://wiki.s4.io/Cookbook/Cookbook Currently it only has: UsingEclipse 1. Check out sources from git 2. Create Eclipse configurations: mvn eclipse:eclipse 3. Import project into Eclipse 4.…
Earlier quoted context omitted.
My attempt at a more friendly description of S4 (based on my very limited understanding of it - please correct me if I'm wrong): When processing large amounts of streaming data, you have to process the data as fast as it comes in or else you can't keep up. You probably wonder: "Why not simply delay the processing of new data while the old data is being processed?". The problem lies in the fact we're dealing with a st…
Thank you for this. Yahoo! should copy and paste your comment onto the S4 homepage.
I wish I had heard about this a few months ago. I wanted to implement a way to create and connect streaming web services. I hacked up something then called webpipes ( https://github.com/dnewcome/webpipes ) using node.js. Unfortunately I haven't looked at it again since I first put it up on github. S4 looks a ton more advanced than anything I was envisioning, but I still think that something simple done in one of the…
The first thing I thought of was this: http://www.supersimplestorageservice.com/