This can increase network performance and move data 300% faster. It is all in the use of machine horse power to better prepare data for transport across the network.

The translation layer automatically translates between data types. Data requests are made via their context which is a universal view of the data.

For example: You could define this view using any kind of data structure, you could even make up your own kind of data types. The system relates the semantics of data typing to a brand and implementation of a specific database system. Known translation are automatically applied while the data is in route.

In some ways yes, naturalized data can conform contextually, but, a context can ignore the boundaries of tables and schema and even of database implementations.

For example: A context can treat some columns from table A and some other columns from table B as a single virtual table.

Any database management system with a Java driver is compatible. This includes the new more application specific database engines.

The current release is focused on universal database access. We intend to add support for non-structured data as that part of the system continues development.

It is surprisingly fast, a complex database implementation with 50 tables averaging 30 columns each can be set up in as little as 6 minutes.

Training on high-level implementation takes between 10 and 20 minutes. Training on lower level aspects takes between 50 minutes to 2 hours.

There is no requirement to maintain at the code level. System adjustments are made via a high level GUI (the same one that does the original high level implementation).

No, there are only two classes required for all data interactions. In fact, you can use databases by simply referencing the context and the server will automatically generate the SQL. Although you can still use traditional SQL against any of the unified databases.

To use our client-side API, yes, the API (and the system) are in Java. You can use any language using a message formatting technique.

No, in fact the unified method uses far less bulk then modern methods, and only a fraction of the data transportation overhead.

All of the experts agree that governance is the key to a successful SOA. But there is a catch 22 in this concept. The experience and knowledge to implement effective control over the technology is needed before you start.

The reality is that it is a process that does evolve. One way to start is to have a working map of the data flow in the enterprise.

Implementing a smart enterprise service bus will address data integration and cause the by-product of a complete data map.

Your data can then be used on an enterprise scale and it becomes a valid foundation for SOA. Governance can then be established before the next step of dividing application components across the network.

Build a solid foundation for both the business management (governance) and technology.