Agile ETL

The classic model for Extract-Transform-Load or Agile ETL, is a tried and true method of gathering data, validating, aligning, and delivering it to one data source at a time. Neither the tools nor the methods have advanced for at least 30 years, making the current process cumbersome.

With the surge of interest in accessing data for business intelligence, and the need for more agile data access, it becomes quite clear that there needs to be a better approach. A single process to read live data, federate, and deliver it to the destination exactly as needed.

Learn more about Agile ETL here
"Legacy ETL"

Extract. Stop. Transform. Stop. Load. Stop.

ETL starts out and ends with some important drawbacks

  • ETL is a one-to-one integration. This means that if it is not a pure on-to-one integration, perhaps one that needs a bit of data from another source, you must save the data in a staging database in order to make it useful. The impact over time of this characteristic has led to a tremendous proliferation of staging databases, data marts, and data warehouses, resulting in staggering tech debt for maintenance and synchronization. How long does it take to get a project lined up with IT to make a new set of data available? Six months?
  • A data model is necessary to define a useful endpoint or staging database. This means that in order to reuse the model for other purposes, the model must be modified or augmented, eventually ending in a nearly impossible support situation.

There are a host of other drawbacks that now weigh heavily on many corporate IT teams and budgets.

The IT world is changing rapidly, and ETL simply is not sustainable. Meanwhile, the need for bulk load types of activities is not likely to go away.

Agile ETL with Enterprise Enabler

Stone Bond’s Agile ETL virtually eliminates the tech debt with the fastest time-to value on the market. Instead of hard-coding with ancient scripting languages, Enterprise Enabler® is a single platform that supports not only ETL, but makes all components of integration reusable for any other integration patterns such as EAI, SOA, and Data Virtualization.

In just a few minutes, one can configure an Agile ETL, test it, deploy, and monitor it all without leaving the single UI driven environment.

Agile ETL is clearly the only path forward for a company that wants to be able to quickly respond to business opportunities and lose the ballast holding IT back.

Why Stone Bond's Agile ETL?

  • All Endpoints. The proprietary AppComm™ technology incorporates data from any source that can electronically convey information, leveraging whatever features that endpoint has available. Rather than convert data to a standard intermediate form, the AppComms access data live and pass it to the transformation engine as it requests interaction with the endpoint.
  • Federation. Agile ETL is not one-to-one. The platform supports configuration of relationships across any number of disparate endpoints, as opposed to passing each source’s data in separate steps to the staging data base.
  • Transformation Engine. Enterprise Enabler’s transformation engine supports any mapping, formulas, validations, etc. as it federates the data from multiple sources. Embedded C# and VB.Net editors and compilers allow rapid coding of snippets of logic, which become part of the metadata instructions.
  • Orchestration. Once the data mapping is configured, Enterprise Enabler’s Process Designer is used to drag and drop the triggers and surrounding logic, additional validations, notifications, execution of other applications, etc.