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 Boris Lublinsky on Feb 16, 2009
A new Forrester research report on the current Enterprise Service Bus (ESB) offerings starts by defining ESB as a core SOA infrastructure:
Most SOA efforts rely heavily on one or more ESBs as their core software infrastructure. This is because an ESB bundles solutions to many different challenges in a single product. ESBs, for example, route multiple protocols and map multiple data formats; create composite services to externalize standard behavior; do data-based routing and service-level agreement (SLA) monitoring and management; and integrate with security infrastructure.
According to the report, the core functions, which provide the basic operational capabilities of the ESB, include:
In addition to the base functionality, the report also defines a set of extended functionality often found in the modern ESBs, including:
Forrester’s evaluation takes into consideration both the above features and product's strategy and market presence. The results of their comprehensive evaluation can be summarized as follows:
- Progress Software, Oracle, Software AG, IBM, and TIBCO lead the pack. These vendors do it all, and they do it all well. All four of these vendors’ solutions include very broad feature sets that include support for many protocols, interaction models, file formats, error handling features, and more. They all have the strong tool sets that let Eclipse-based developers work with design artifacts graphically.
- IONA, Sun Microsystems, and JBoss offer competitive options. Both IONA - now owned by Progress - and Sun fall in the middle of the pack, but for very different reasons. IONA’s Artix and FUSE products are established and successful, especially with customers that want the lightweight-endpoint approach IONA offers. Sun Microsystems’ strongly standards-compliant Sun ESB Suite offering is simply too young to have a feature set like those of the Leaders’ solutions, though its trajectory suggests future growth in both capability and adoption. Though Sun ESB Suite is a community-developed open source product, it is clearly heavily dependent on Sun’s involvement, at least for the foreseeable future. JBoss has a strong core ESB engine, popular with developers in shops that favor open source. It has limited but growing enterprise features and lacks graphical tooling and the breadth of options the older products offer.
- Microsoft offers strong core ESB functions for BizTalk customers. Windows-centric customers with existing BizTalk implementations and the appetite for a little "assembly" will find that Microsoft’s ESB offering is a product with strong ESB capabilities and - a pleasant and welcome surprise - a strong ability to integrate with services on other platforms. Microsoft’s main challenge is that it provides its ESB solution essentially in kit form - freely available "ESB Guidance" information and software that the customer must graft onto the combination of Microsoft BizTalk Server and Windows Communications Foundation (WCF). ESB Guidance does include a full reference implementation of a working ESB with all the components integrated. Also, both the developer and application code must directly manipulate XML artifacts because the solution does not provide a graphical editor. The solution runs only on Windows, which limits its applicability in shops that need to deploy their ESB to other platforms.
- MuleSource has a strong core but a narrower feature set. Like the JBoss product, MuleSource’s offering has a strong core ESB engine and is very popular today with developers in shops that favor open source. Though Mule ESB is evolving, it currently has limited enterprise features and fell short on graphical tool sets, broad protocol and application adapter libraries, and critical partnerships.
The report is packed with a wealth of information on existing ESB products and the results of their evaluation. It is a good starting point for everyone who is doing an initial ESB products evaluation.
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