<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: TIBCO disappoints</title>
	<atom:link href="http://jeffnolan.com/wp/2006/09/29/tibco-disappoints/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffnolan.com/wp/2006/09/29/tibco-disappoints/</link>
	<description>Jeff Nolan&#039;s take on investment, innovation, entrepreneurship and the technology industry</description>
	<lastBuildDate>Mon, 06 Feb 2012 06:44:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Anshu Sharma</title>
		<link>http://jeffnolan.com/wp/2006/09/29/tibco-disappoints/comment-page-1/#comment-28996</link>
		<dc:creator>Anshu Sharma</dc:creator>
		<pubDate>Sat, 30 Sep 2006 21:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://jeffnolan.com/wp/2006/09/29/tibco-disappoints/#comment-28996</guid>
		<description>Tibco is going the way of Vitria and SeeBeyond. The EAI niche has been subsumed and the demise of the likes of Tibco brought about by two factors:

1. Web Services &amp; Standards: This makes integration technology a commodity. As more of your applications come with Web Services (or at least open APIs) for integration, the customer is less willing to spend on million dollar tools or message brokers.
2. SOA: An enterprise looking to solve the messaging or EAI problem may have seen TIBCO as best of breed but when your EAI/Messaging problem is a subset of your SOA initiative, you are much more likely to go with a big platform vendor like Oracle, BEA, etc.


(In full disclosure, I work for the Oracle.)</description>
		<content:encoded><![CDATA[<p>Tibco is going the way of Vitria and SeeBeyond. The EAI niche has been subsumed and the demise of the likes of Tibco brought about by two factors:</p>
<p>1. Web Services &amp; Standards: This makes integration technology a commodity. As more of your applications come with Web Services (or at least open APIs) for integration, the customer is less willing to spend on million dollar tools or message brokers.<br />
2. SOA: An enterprise looking to solve the messaging or EAI problem may have seen TIBCO as best of breed but when your EAI/Messaging problem is a subset of your SOA initiative, you are much more likely to go with a big platform vendor like Oracle, BEA, etc.</p>
<p>(In full disclosure, I work for the Oracle.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Wood</title>
		<link>http://jeffnolan.com/wp/2006/09/29/tibco-disappoints/comment-page-1/#comment-28694</link>
		<dc:creator>Jason Wood</dc:creator>
		<pubDate>Fri, 29 Sep 2006 19:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://jeffnolan.com/wp/2006/09/29/tibco-disappoints/#comment-28694</guid>
		<description>As long as I don&#039;t have to be our version of Tucker Carlson, count me in. :)</description>
		<content:encoded><![CDATA[<p>As long as I don&#8217;t have to be our version of Tucker Carlson, count me in. <img src='http://jeffnolan.com/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

