Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Niclas Nilsson on May 23, 2008
Today, in about an hour (4 PM GMT+2), there is a public load test on the Google App Toolkit at http://qwerty.codathlon.com.
Didier Girard, an expert on Google Web Toolkit and Rich Internet Applications, has built a plain vanilla GWT app hosted on the Google App Engine infrastructure. And he is confident it can take a quite high load.
I have built it with no special optimization. I mean that I try to avoid classical bottlenecks, but I have coded it like most developers will code it. I’m pretty confident that the Google App Engine can welcome a large traffic. I think also that GWT is particularly suited for high traffic. Now, it is time to prove it.
In about an hour from now, he want’s a few thousand visitors.
My objective is simply to get 4000 unique visitors in 10’. I think it is equivalent to get 100000 unique visitors a day : 100000 / 4 hours / 6 . This is not that much, but I think it is enough to show that 99.9% of websites can be coded in GWT and hosted on GAE without thinking about the slashdot effect. If you want to be part of the team, just go there “http://qwerty.codathlon.com” on Friday May, 23 around “4 PM GMT+2” (depending of your time zone). If you want to help me in this effort, just spread the word.
So let’s find out if Google Web Toolkit on Google App Engine can handle the InfoQ effect.
Mobile and the New Two-Tiered Web Architecture
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Monitor your Production Java App - includes JMX! Low Overhead - Free download
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
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.
1 comment
Watch Thread Reply