Avaki Corporation releases Avaki 5.0
April 13, 2004
Avaki today announced the release of Avaki 5.0, an enterprise information integration solution that simplifies provisioning, access and integration of data from multiple, heterogeneous, distributed sources. In addition, you are able to plug in third party data integration tools, such as ETL tools, query tools or third party profiling tools, and use the tools in a real-time manner. In essence, this lets you bring all of your tools under one umbrella rather than having a hodgepodge of approaches with numerous tools isolated in their own departments. They can all be available through this one data services layer, allowing any project to re-use efforts from other projects.
What's new in this release:
- Expanded integration capabilities - Data integration capabilities needed to aggregate two or three result sets coming from different databases have been expanded so that they behave as a single result set.
- Added Enterprise Data Integration Framework - Third party tools, such as an existing ETL engine, existing cleansing tools, may be plugged into the product and made available as a service within the grid.
- Web services support - Web services support has been added for a number of Avaki's capabilities and auditing capabilities have been expanded so that it is now possible to track what applications or users are using what data, what transformations have taken place, etc. This is an important feature due to the current compliance movements.
The three layers of Avaki:
- The Provisioning Layer
In the provisioning layer, the data owner can make any type of data available, whether it be relational data, (coming straight from a database), application data, (that is being provisioned through an API), or even file data. The SQL Statement or stored procedure is published as an object within Avaki using a data catalog, which is a registry for all of the operations that go on within the system. Within this layer, access controls may also be applied to the object, as well as specifying when the query will be run, and tracking the usage of the data that has been made available.
- The Access Layer
The access layer is the layer where an application goes to find data, (even though that data may be physically located in multiple places). Again, the data catalog or registry is used, along with a search function. The data can be rolled up as a single view, or it can be a result set from one query from one database. Users or applications see only the data that is available to them, but it appears as if all of the data is local when in fact, it may be distributed around the world. Both read and write functions are available, allowing the user or application to write back to the data sources. All of this can be accomplished through various protocols: as a web service, through SOAP, or via standard database protocols - JDBC, ODBC, or standard file I/O operations.
One thing of interest to note is that Avaki protects the data source and speeds up the access process for an application by allowing you to pre-run a query with the results being cached in the Avaki system. The user can determine how often the cache is to be updated, under what circumstances, or in response to some event.
- The Integration Layer
The integration layer is where you can take the data that has been provisioned, and aggregate it or do transformations against it before it is delivered to the application. Data from multiple sources can be aggregated and made available as a very coarse-grained data service.
There are a number of ways that Avaki provides for this integration.
- Data Services - the ability to dynamically create a transformation or aggregation, driven y parameters, in either Java or XSL and publish it into the data catalog as a reusable service.
- Data Grid Query - The operation in Avaki that allows one to submit a SQL statement and run a single query against multiple databases at once. The query is distributed across two or three different databases and the result is brought back into Avaki.
- Generated Views - These are similar to data services except that they are static and they do not take parameters. Generated Views may be run on a scheduled basis or based on some kind of an event.
- Third party tool integration - Avaki allows you to plug in third party tools and make them available as a service.
Additional information can be found at Avaki's website.
Avaki Corporation provides enterprise information integration software that simplifies how businesses provision, access and integrate widely distributed data from many heterogeneous data sources. Avaki enables businesses to use fresher, more accurate data, while reducing the overall cost and complexity of data integration infrastructure, programming and maintenance. Customers such as Pfizer, Aventis and Pacific Capital Bank are using Avaki software to reduce data integration costs, make fresh data available, and improve productivity. Backed by Polaris Venture Partners, General Catalyst, and Sofinnova, Avaki is located in Burlington, Mass.