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 Udi Dahan on Dec 10, 2007
Microsoft Live Labs has released Volta - a technology preview of a developer toolset that will enable developers to build multi-tier web applications faster. Announced under the slogan "Web application development using only the materials in the room", Volta allows developers to target either web browsers or the desktop by handling tier-splitting under the covers.
While some have decried the black magic occurring behind the scenes, other quote Martin Fowler's First Law of Distributed Object Design:
Don't distribute your objects!
Indeed, enough has been written on the dangers of careless distribution. Dan Creswell, however, adds context to the above law which appears to bring Volta back into harmony with the distributed systems community:
Network round-trips are often considerably less costly than the time taken for a transactional database operation due to the need to forcibly log transactional operations which is very costly in terms of disk performance. i.e. network round-trips aren't always the performance bottleneck.
Microsoft explains their reasoning for releasing Volta as an "experiment" as:
[To allow] for testing of the model with customers and partners in order to gather early feedback and continually influence the direction of Live Labs technologies and concepts.
Yet this experiment comes with deep considerations around tiered deployment:
Volta automates certain low-level aspects of distributing applications across multiple tiers, allowing programmers to devote their creative energy to the distinguishing features of their applications.
Via declarative tier splitting, Volta lets developers postpone irreversible design decisions until the last responsible moment, making it faster and cheaper to change the architecture to accommodate evolving needs.
Through MSIL rewriting, Volta follows developer's declarations to turn a single-tiered application into a multi-tiered application, generating boilerplate code for communication and serialization.
Finally, the team from Live Labs is making the issues and limitations of Volta be known up front - information critical for any architect to know before employing it in a development effort:
Although not part of any technology roadmap, the impact of this vision on the future of web development on the .NET platform should not be dismissed. For more information on Volta, take a look at this video available on Channel 9: Erik Meijer: Volta - Wrapping the Cloud with .NET part 1 and part 2.
arbitrarily moving the distribution border and disregarding the fallacies of distributed computing by trying to treat the network as transparent are recipes for failure.
I explained this further on my blog
This is just insane. It would be really cool if it works, but every fiber in my being is saying this cannot end well.
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.
2 comments
Watch Thread Reply