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 Dilip Krishnan on Dec 03, 2008
Nick Gall comments on the Gartner WOA report which he co-authored. The report starts by defining WOA; as an extension of Roy Fielding’s definition RESTful architectures, with respect to the four uniform interface constraints in particular.
The key take-away from the report is that the application neutrality constraint is a fundamentally important constraint; and when applied to an SOA, it allows for global network effects in terms of serendipitous reuse.
According to Nick, the Gartner report is a result of consensus between Anthony Bradley, Dan Sholler and himself and represents Gartners position on WOA in relation to the WS-* specifications.
The report notes that
The primary problem with the specifications known as WS-* (such as SOAP, WSDL and UDDI) is that their principal emphasis is on implementation neutrality. […] Although this is not an unworthy goal […] it shifts the focus from the generic interface constraint of application neutrality.
Application neutrality should be the principal goal of an interface, because it is precisely this characteristic that enables shareability (a fundamental SOA principle).
The key to shared use (reuse) is a generic, application-neutral protocol, such as the Atom Publishing Protocol (APP) or Google’s GData Protocol. Conversely, the more application-specific a protocol is, the less shareable it is.
Nick concludes by quoting the report "The goal is to focus on the key generic interface constraints that unite these [REST, WOA, Web Services] concepts, not debate the nuanced differences among them."; which he believes is what will put the power of the “Web” back in “Web Services”. The report is available in the Gartner web-site.
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.
No comments
Watch Thread Reply