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 Jonathan Allen on Jan 06, 2009
One of the advantages of a REST architecture is that is makes it much easier to implement cross-language bindings. To wit, Sriram Krishnan has created a set of Azure bindings for the concurrent programming language, Erlang.
Erlang is a language developed specifically for concurrent programming. It uses a message passing model and "processes" instead of threads. Erlang processes don't have a good corollary in platforms like .NET. They are lightweight, requiring much less memory than normal Windows threads. They are also cheap to run, with a cost comparable to a function call rather than a context switch. Code-wise, a process looks like a normal function paired with a message queue. The runtime pulls messages from the queues, passing them to the process's function one at a time.
If you are interested in learning more about Erlang, check out Sean Hinde's Erlang for C, C++ and Java Programmers. As for Siram's Erlang Bindings for Azure, they are available at Github.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Modeling Your Cloud Services Brokerage
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
If you are interested in learning more about Erlang, check out Sean Hinde's Erlang for C, C++ and Java Programmers.
Better fix that link to: Erlang for C, C++ and Java Programmers.
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