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 Aug 08, 2008
1. Multi-channel Applications
2. Composite Applications
3. Business Process Orchestration
4. Service Oriented Enterprise
5. Federated SOA
The strategic planning assumptions in the article, point to some key trends in the timeline for adoption of these patterns in the enterprise
(To paraphrase)
By 2008, more than 66% of new midsize and large interactive applications will be designed to support multi-channel access, up from less than 33% in 2007. Multi-channel Application is a pattern that separates the back-end business logic from the front-end logic and delivers full application functionality to a maximum number of users from various channels. As this increases we will see an increased investment in building composite applications.
By 2009, more than 75% of SOA applications will implement some sequencing control outside of code of the service implementations, via external BPM technology.
By 2010, more than 85% of enterprises will become service oriented, and will have combined their application integration and SOA management tools and organizations.
Through 2012, the majority of SOA-style applications will be interactive composite applications
Finally, considering the number of mergers and acquisitions, Federated SOA is becoming more relevant. The fundamental idea behind federated SOA is to logically split the enterprise into semi-independent SOA domains, each with its own specific SOA infrastructure, governance processes and SOA Center of Excellence.
Be sure to check out the original post for more insight.
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