We are hiring!

Xtivia, Inc.
2012 North America Liferay Partner of the Year

Join our top-notch team of Enterprise Java and Liferay Portal professionals in our Austin, TX office or work remotely! Please check out our current Dice listings.

Recent Bloggers

Luke Smith

Posts: 9

Stars: 0

Date: 5/24/13

Brian Fairchild

Posts: 19

Stars: 0

Date: 5/16/13

Mangesh Mharolkar

Posts: 10

Stars: 0

Date: 5/7/13

Barrie Shaw

Posts: 4

Stars: 0

Date: 4/17/13

Andrew Dalby

Posts: 2

Stars: 0

Date: 4/5/13

Tina Xing

Posts: 1

Stars: 0

Date: 3/29/13

Kaushik Nagaraj

Posts: 7

Stars: 0

Date: 3/27/13

Asier Del Pozo

Posts: 3

Stars: 0

Date: 3/27/13

Chris Shaw

Posts: 1

Stars: 0

Date: 2/26/13

Bin Zhu

Posts: 4

Stars: 0

Date: 2/24/13

« Back

A Different Perspective on ETL needs

6/28/12 5:37 PM

Changing business condiitions drive changes in business requirements (sometimes like wildfire, utterly unpredicatable) I have been through this situation numerous times, as I am sure you have been as well. So how to respond to these changing conditions? What if we have to break the ETL architecture that we have built?

As I was thinkging about this, a thought occured to me. May be we don't have to be slaves to one set of standards but just be proactive in our approach. I hope the following table would be helpful in giving you a good insight or at the very least start a new thought process...

Factor	Efficient ETL Architecture Requirement
Architecture strategy	Standardized Reports; emphasize high volume usage
Data Throughput cushion	Low; Generally data sizes are well known and do not change arbitrarily
Data Storage	Low; enable high inventory turns
Lead time	Shorten, but do not increase costs
Source System selection	Emphasize low volumes (deltas), consistent quality, on-time delivery
Demand	Predictable, Amount of data sourced does not change dramatically
Priorities	Low cost, consistent quality, on-time delivery
New Data Source introduction	Infrequent
Data variety	Low

Factor	Responsive ETL Architecture Requirement
Architecture strategy	Assemble-to-order, make-to-order, or customized service or products; emphasize variety
Data Throughput cushion	High
Data Storage	As needed to enable fast delivery time
Lead time	Shorten aggressively
Source System selection	Emphasize fast delivery time, customization, variety, volume flexibility, top quality
Demand	Unpredictable; Generally in the form of data dumps (of large sizes)
Priorities	Development speed, fast delivery times, customization, volume flexibility, variety, high reliability
New Data Source/s introduction	Frequent
Data variety	High