New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Niclas Nilsson on Sep 07, 2007
Today there are 3845 applications on Facebook. Why are so many developers attracted to the Facebook platform? One of the answers is that Facebook learned from the mistakes that MySpace made.
The Facebook Platform is only about three months old; yet it has attracted 70,000 developers. No wonder since the user base is more than 30 million people, but Facebook also realizes that these developers are important to them.
In a recent article, Dare Obasanjo analyzed how MySpace managed to devalue their platform by making three mistakes; mistakes that Facebook seems to have avoided successfully. Dare writes:
So, why would developers who’ve witnessed the success of companies developing MySpace widgets rush to target a competing social networking site that has less users and requires more code to integrate with the site? The answer is that MySpace made the mistake of thinking that they were a distribution channel instead of a platform. If you are a distribution channel, you hold all the cards. Without you, they have no customers. On the other hand, if you are a platform vendor you realize that it is a symbiotic relationship and you have to make people building on your platform successful because of [not in spite of] your efforts.
Sure, Dare is employed by Microsoft and MySpace is in business with Google so there may be politics going on, but that does not make his arguments less interesting from the entrepreneur developer perspective.
The three classic mistakes that MySpace did according to Dare are:
About a year ago, MySpace explained that since most traffic to YouTube, Flickr and Photobucket (now owned by MySpace) came from their site, they could easily build such services themselves and create a parallel business and either match them or exceed them. Not really a mashup way of thinking?
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
No comments
Watch Thread Reply