RIM Server Crash Leaves Millions Without BBM
Several readers have sent word that "tens of millions of BlackBerry users in Europe, the Middle East and Africa have been unable to receive or send emails and messages through their phones, following an outage at the server systems of parent company Research In Motion." RIM has confirmed that they're aware of the problem and working to restore service. A former RIM employee said to The Guardian, "They didn't start looking at scalability until about 2007, when they had around 8M active devices. The attitude was, 'We're going to grow and grow but making sure our infrastructure can support it isn't a priority.' They have their own clunky infrastructure to do something that you don't really need a clunky infrastructure to do anymore."
If Blackerry was still popular.
Or if it happened to BlackBerry....with their 70M subscribers.
0 = 1 + e^(Alt something)
Okay, why does a disgruntled ex-employee's rant about scalability and infrastructure come into play before we know that scalability or infrastructure was the cause of the break? Seriously, maybe the taco bell dog just chewed through fiber lines in NY and LA while on tour. Could happen to anybody.
-- IANAL, this isn't legal advice, and definitely isn't legal advice for you. Also, Squee!
... they just don't know it yet. We have 40 Blackberry's in our company, but we purchased our last one about six months ago. I hope BES dies a painful, painful death.
Android, here we come.
----- obSig
If they had simply used DNS names, they could fail-over on many levels simply by re-pointing DNS.
Maybe they were worried about DNS poisoning or something like that. Still should be a way to remotely update those "service book" addresses though.
The higher the technology, the sharper that two-edged sword.
It's as if millions of souls cried out ... and were suddenly silenced.
And, you know, SQL databases, too, since they scale very well.
BTW, why do you jump to the datastore as the scalability problem? It's not mentioned in the article. For all we know, it could be their internal Cisco routers that are overloaded or their WAN links or their 10-year-old Windows 2000 servers or something else.
Advice: on VPS providers
In four years I'll be starting a company based on the idea of having a device that stores all your photos, emails, and applications locally so you aren't tied to the cloud.
No, it doesn't mean any such thing. I take it you've never heard of CARP or VRRP.
You are stuck with RIM service if you want a blackberry handset, you don't have a choice unless you switch to a different type of handset.
Complete nonsense. Even without RIM service, it still functions as a phone, internet access, and SMS text messaging. Basically everything you use a smartphone for. You just dont have access to the secure RIM enterprise data and messaging services. Neither does any non BB device, so basically the BB just downgrades to a standard smartphone.
Tesla was a genius. Edison however was a overrated hack who liked to torture puppies.
He's jumping to the datastore because he can't cunningly fit in a link to his presentation about NoSQL database software if he doesn't.
A campaign against RIM has been running in the media for the last few months. Before the iPhone and Android devices there was the Blackberry and I bet RIM still have a few cards left up the sleeve.
> if you look in the "service books" of a Blackberry device, you will find a lot of hard-coded IP addresses. This means that RIM is pointing all devices to a single server in a single data center on the end of a single circuit owned by a single provider.
Following this "logic", by using DNS it would have been possible to do what, change the single server in that single data center to another single server in another single data center? Or is it only when you use DNS that it becomes possible to do load-balancing and clustering?
> Some real morons running the show over there
Oh yeah, clearly the morons are over there
lucm, indeed.
Wow, another Slashdot hatchet job on RIM. Heavy into Apple stock, are we?
RIM certainly has issues, and it may not survive. But it seems the Slashdot editorial staff wants to make sure.