Comments on: An Interesting Mash-Up http://www.architected.info/blog/an-interesting-mash-up How people, practices, and information are transformed into relationships and understanding. Fri, 12 Mar 2010 00:54:46 +0000 http://wordpress.org/?v=2.0.6 by: Architected Information » Enterprise Web 2.0, Linux, and Ecclesiastes http://www.architected.info/blog/an-interesting-mash-up#comment-323 Tue, 22 Aug 2006 01:40:57 +0000 http://www.architected.info/blog/an-interesting-mash-up#comment-323 [...] Dion Hinchcliffe has been writing some interesting stuff about web 2.0 in the enterprise. His latest post is a bit of a rant against Wikipedia, but push on and it is worth the read. Lately I have been pondering the impact of things like SOA and mashups in the enterprise context, blending in the web dialtone discussion that is happening on the O’Reilly Radar. [...] […] Dion Hinchcliffe has been writing some interesting stuff about web 2.0 in the enterprise. His latest post is a bit of a rant against Wikipedia, but push on and it is worth the read. Lately I have been pondering the impact of things like SOA and mashups in the enterprise context, blending in the web dialtone discussion that is happening on the O’Reilly Radar. […]

]]> by: morgan http://www.architected.info/blog/an-interesting-mash-up#comment-70 Tue, 25 Jul 2006 01:15:53 +0000 http://www.architected.info/blog/an-interesting-mash-up#comment-70 Thanks for your feedback about Cast Iron. I haven\'t used it myself, but I think that appliances could be the next step in the ETL market. Probably a good way for someone to attack the low end of the market, then move upstream. Also, I appreciate your distinction on <a rel=\"nofollow\" href=\"http://en.wikipedia.org/wiki/Real_time\" rel="nofollow">real-time</a> vs. <a rel=\"nofollow\" href=\"http://en.wikipedia.org/wiki/Near_real_time\" rel="nofollow">near-real-time</a>.  However, I would disagree with your assessment about the value of faster processing in the data warehouse.  I am currently working in a near-real-time data warehouse, where our data takes less than 15 minutes to go from data collection to reporting. While I am not sure of the economic benefit of processing any faster, I can say that we are able to give our organization a distinct and tangible competitive advantage with our turnaround time. Thanks for your feedback about Cast Iron. I haven\’t used it myself, but I think that appliances could be the next step in the ETL market. Probably a good way for someone to attack the low end of the market, then move upstream.

Also, I appreciate your distinction on real-time vs. near-real-time.  However, I would disagree with your assessment about the value of faster processing in the data warehouse.  I am currently working in a near-real-time data warehouse, where our data takes less than 15 minutes to go from data collection to reporting. While I am not sure of the economic benefit of processing any faster, I can say that we are able to give our organization a distinct and tangible competitive advantage with our turnaround time.

]]> by: Anonymous for legal reasons http://www.architected.info/blog/an-interesting-mash-up#comment-64 Mon, 24 Jul 2006 00:19:42 +0000 http://www.architected.info/blog/an-interesting-mash-up#comment-64 I've used Cast Iron Systems tool and I would hardly call it ETL worthy. It truly is EAI, and probably pretty good at that but we tried to use it for ETL and it does not fit the mold. The product was just too slow and not enough functionality for true ETL. Beware if the term "Real Time ETL" or "Real Time ETL-Lite". Real Time Datawarehousing isn't very practical and if any part of that process is batch then you have a batch process not a realtime process. I have seen tools advertising as real time ETL such as CastIron and thats a fancy way of saying we do EAI, not ETL. I’ve used Cast Iron Systems tool and I would hardly call it ETL worthy. It truly is EAI, and probably pretty good at that but we tried to use it for ETL and it does not fit the mold. The product was just too slow and not enough functionality for true ETL. Beware if the term “Real Time ETL” or “Real Time ETL-Lite”. Real Time Datawarehousing isn’t very practical and if any part of that process is batch then you have a batch process not a realtime process. I have seen tools advertising as real time ETL such as CastIron and thats a fancy way of saying we do EAI, not ETL.

]]>