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 Jonathan Allen on Jun 08, 2007
A new project called Browsershots allows web designers to see what their site looks like in a multitude of browsers and platforms with a trivial amount of effort.
When you go to Browsershots, all you have to do is enter a website and check the browsers you want to test. It supports 31 Linux browsers, 6 Windows browsers, and 2 Macintosh browsers. These counts include both variants such as MSIE 6 and 7 as well as rare browsers such as Iceweasel and SeaMonkey.
A collection of computers running the various operating systems and browsers open the provided site and take screen shots. These are then presented to the designer, if he is patient enough to wait for them.
A serious problem with Browsershots is that it can literally take hours to get back all of the screenshots. There is a publically available queue to let you know where you are in line, but unless it is really short you should use the maximum timeout on your request. Currently that is 4 hours.
The service currently describes itself as a Technology Preview and is free of charge.
Umm, Browsershots is at least 2 years old... it's been a "technology preview" for that entire time. Not to say it's not cool.
I've always used www.browsercam.com/ for that - but you'll have to pay after the trial period (of only 24 hours).
A problem with screenschots is that you can see what it looks like, but not if the interactive parts will work - which could be a problem if you use javascript.
But 31 browsers for Linux !?!?!? Too funny.
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.
3 comments
Watch Thread Reply