Scroll

Exago Blend - Succeeding Traditional ETL

Exago BI easily combines disparate data sources into a single reportable data model. Most organizations have experience leveraging traditional SQL databases like Microsoft SQL Server, Oracle, or PostgreSQL. These sources are perfect for storing and retrieving relational user records or product manifests. NoSQL data stores like MongoDB are becoming more popular options for data that is not well defined, and that caters to systems like data mining, word frequency analysis, and file content management.

Many companies utilize two or more different data sources, and therefore require a reporting solution that not only supports every data source, but can also combine their data together and report off of it in a meaningful and transparent way.

Traditionally this would be done through use of an ETL layer, such as a data warehouse, that performs the requisite data merging in a tertiary database, often at timed intervals. The reporting solution would point to this database instead of the original sources. But traditional ETL is not an appropriate solution for everyone, due to the complexity it can add to a reporting environment and the data latency induced when reporting against an ETL database.

Exago BI does not need a separate ETL layer to join across data sources. Instead joins are done in-memory with a technology called Blend.

Blend is a parsing and recombination engine that parses the elements of individual data queries into in-memory storage, then collects them into a unified database-neutral expression tree. The tree data structure allows for efficient retrieval of requested report data.

Blend.png

Blend allows administrators to define direct join paths between entities belonging to entirely separate data sources. The sources do not need to be on the same server, or even in the same physical location. All that matters is that Exago BI can connect to them. Any and all of our supported data sources can be merged together. Joins are defined in the data model, completely independent of the sources themselves. And this is done in exactly the same manner as with single-source joins, using the Administration Console.

Defining join paths is the only requirement to enabling Exago Blend. Executed reports that require data from multiple sources have their independent queries parsed in the background. Blend re-configures the data in-memory to create a single data set for reporting. None of this data is cached by default and each report execution has real-time data.

Exago BI allows end-users to create reports without needing any knowledge of the underlying data model and without needing to write SQL. All that users will see is the data itself. So data from sources as different as SQL and MongoDB can be used together seamlessly, with no friction to the end-user experience.

Sources.png

Exago Blend can succeed a standalone ETL warehouse for connecting between multiple databases, which can simplify reporting environments and increase the accuracy of on-demand reporting.

Or Blend can be a complement to ETL. Organizations are not limited to choosing one or the other. Exago BI can join between a warehouse and a transactional database, or even between multiple warehouses, if the need arises. All sources look the same to Blend.

For more information, please file a support ticket or contact us via the Try Exago link on our home page.


Hidden Article Information

Article Author
Exago Development
created 2018-04-19 14:25:00 UTC
updated 2018-04-19 20:59:33 UTC

Labels
data, load, transform, SQL, memory, process, join, source, cross, storage, blend, etl, extract, warehouse, mongodb, mongo, oracle, in-memory, processing, nosql,
Have more questions? Submit a request