So Twitter is down, again.
Twitter, a great idea, but terribly designed and implemented…
Twitter is a great case study:
- for what a badly designed piece of software is all about,
- for what not do, or what to avoid, or how NOT to architect and deploy software (i.e. by avoiding everything they have done so far),
- for how to NOT design and deploy your SaaS system.
But not everything is negative here; there are a lot of lessons learned, I am sure… I wouldn’t mind taking a look at what they have done, again, as a case study…
And maybe the folks at Twitter should write a book (or set of articles) on the things to avoid / not to do, when designing networked, high-availability web-based, messaging SaaS-based systems…
Update (June 8): Bad design, but perhaps, bad capacity planning….
ceo