The lady doth protest too much, no? The guy is using Redis as a buffer to what ultimately ends up just being a central log file. You know. rsyslog. None of the fancy things you have in mind. Which brings me to the same point someone's already made: using Redis buys you nothing, even if you had a more involved use case in mind.
Saying that he can do something by subscribing to an event in Redis is sorta silly, isn't it? You could just as easily tail the logs, as many systems actually built for this purpose do. Once again, there are already things in *nix for this.
The reality is, this is a janky, nubile solution to an already well-solved problem that is now getting thousands of views because of HN and antirez tweeting about it. Instead of learning the correct way of doing things, I bet a bunch of inexperienced developers are now going to say "BOY THIS IS SWELL" and cut themselves a nice fat chunk of technical debt for the not-that-far-off future.
Edit: err I should probably add more substance than that.. one less thing to keep track of and have to set up when getting into config management = win
So Canonical, a distribution maker, is not to be trusted for their kernel suggestions, but Amazon is infallible? On what basis?
We asked the Amazon kernel team if we should try switching to one of their kernels/distros, and they said "No, just upgrade to Maverick and the accompanying kernel." It's been pointed out that Maverick has its own set of Xen bugs. I guess Amazon doesn't know everything.
The horse you're getting on about using the "proven" Amazon kernels is a bit high. Turns out this whole virtualization thing is somewhat new, and the kinks are still being worked out. Old kernel builds don't work particularly well because a lot of their assumptions are broken by virtualization; new kernels are what they are - new.
(Edit, forgot initially): Finally, we ran 10.04 - the Long Term Support release of Ubuntu from a year ago. There was no "because we can."
Frankly, I'm a bit amazed at your disdain for people sharing their findings from practical experience running into these issues in high-load production environments.
You're neglecting the fact that which distro you choose has a large influence on the kernel version you get to run. With the amount of work going into stabilizing the kernel when running in a virtualized environment, chaining yourself to a slow-moving distro will cause the exact opposite of stability when running on Xen. See: this blog post.
We ran into what we believe to be this very problem at SimpleGeo and spent a long time figuring out what the cause of the JVM locking up for tens of minutes at a time were; we believe this bug (or general class of bugs) to be responsible. Upgrading to 10.10 has caused the majority of the symptoms to disappear.
My personal hunch is that there are probably startups and developers that dumped Cassandra due to "stability issues," which were in reality symptoms of this bug. There's obviously no way of confirming or denying this, so I'll reiterate that it's just a hunch.
The implication is that the people for whom eventual consistency is not an option will never reach a data set size or availability requirement that'll require them to use replication and experience the lag (and eventual consistency) involved.
I think any serious infrastructure is going to need a cross-language, cross package manager entity that just lines everything up. I've run into the problem with pip on ubuntu where it puts something in the requirements file, but that thing isn't actually in pypi but was installed by apt or worse, if I generated the requirements file on my mac, macports.
I think more examples of how proper config management tools make that sort of clusterfuck manageable would go a long way towards convincing people that if you're expecting your product to have any longevity, you have to pay attention to this stuff and do it right.
Why of course. You can come stay in the closet of my studio apartment. I'll feed you and clothe you until we can find just the right opportunity for your brilliant mind!
I know we're supposed to be "nice," but this is absurd. Go back to school and NEVER say about yourself that you are "dashing" or "charming" - no matter how tongue-in-cheek you try to make it sound, you just come off sounding like the exact opposite.
Upon reading more of your responses, I'm further convinced that you should stay where you are. Nobody cares about your fancy "cross flights." Right now is certainly not the time to abandon everything and come to California.
I like that... I'll have to see if there's a way to locate the stops short of just maintaining a database. I'll also need to be careful with browser detection - I don't want to be loading a Google map on an edge connection. I'm trying to walk a fine line with having a nice user experience and making it usable on ANY mobile device.
Upon my moving to the US in 98, some kids at my middle school found out the hard way that that is certainly not a universal rule.
I certainly do think that hackers are more prone to being inept at social situations (and when I say "social" I don't mean social as in "social network," I mean real interpersonal contact). Since bullying is a kind of social situation, I could totally see how the aforementioned ineptitude could lead to not knowing how to deal with bullies. That's why it's important to have other stuff going on in your life beyond hackery. Sports, sex, parties, music - SOMETHING.
Well, at least at this phase, I'm solving the very specific problem (dogfooding like crazy here, btw) of having a very set routine that can involve N number of busses where N > 1. Instead of having to look up departure times for each bus individually, you just set a bookmark. Now every morning, I just click "To Shuttle" and have everything I need to know.
Stuff like directions is already handled by Google Maps, though I realize that's not available on all phones.
Yeah, but it works on most other phones its been tried on (limited audience so far, but I know it works well on the G1, as well as on some basic browser phones with small screens)
By the way: any feedback as to how it looks on non-smart phones + screenshots would be really appreciated.
Saying that he can do something by subscribing to an event in Redis is sorta silly, isn't it? You could just as easily tail the logs, as many systems actually built for this purpose do. Once again, there are already things in *nix for this.
The reality is, this is a janky, nubile solution to an already well-solved problem that is now getting thousands of views because of HN and antirez tweeting about it. Instead of learning the correct way of doing things, I bet a bunch of inexperienced developers are now going to say "BOY THIS IS SWELL" and cut themselves a nice fat chunk of technical debt for the not-that-far-off future.