How Does 1010data Fit Into My Architecture?

In a typical data warehousing architecture, data comes from operational systems and other sources and is loaded into the data warehouse via ETL (Extract, Transform & Load) processes. The data warehouse, although meant to support analysis and reporting, is often too slow for that purpose so additional components are required. In particular, application-specific data is extracted from the warehouse and stored in data marts or OLAP cubes for use by the application programs. This additional step adds complexity and limits application developers and end users in the kinds of analysis that they can do.

The following diagram shows a typical data warehousing architecure.

As shown in the next diagram, 1010data significantly simplifies the archtecture on both ends. Instead of implementing complicated ETL processes - and buying the requisite software - the data is simply extracted from the legacy systems and sent to 1010data, usually via FTP. Even more importantly, since queries run so quickly against the raw data, there is no need for data marts or cubes. In many cases even BI tools are unecessary since 1010data comes complete with a powerfull, user friendly, browser based interface.