What is Dataworks Enterprise?

Dataworks Enterprise is "Financial Middleware for Servers and Workstations"

Financial?

Although Dataworks Enterprise could be used to distribute any kind of information, i.e. Stock Control, Library Cataloging, etc. it is specifically designed to operate in financial information environment. It has a data model specifically geared to the requirements of the financial markets. For instance, Dataworks Enterprise has special knowlegde of how to compress trade histories.

Middleware?

By middleware, we mean that it acts as a layer between the client application and the sources of data. It provides data to the application through a single standard API using a normalised data model. It also provides caching to reduce the work required of the back-end systems.

Servers?

Dataworks Enterprise is fast enough to operate in the server environment. Most current Dataworks Enterprise production installations are on servers, such as Web Farms and Application Servers. The product has proven that it scales well.

Workstations?

Dataworks Enterprise is small enough to operate in the small confines of a workstation environment. A minimal software install might consist of some Java classes or one DLL and one executable occupying a few megabytes of diak space. Most developer installations of Dataworks Enterprise are installed on work stations.

Middleware gives benefits to the "Consumer" and the "Provider"

Consumer?

The consumer benefits from middleware by simplifying the task of development and deployment of solutions especially where data is being provided through a number of legacy or "data source specific" APIs. By simplifying the task, we reduce the cost of systems, increase their reliability and provide customer organisations with a more rational and integrated view of the company's data.

Provider?

The provider benefits from middleware in that they have fewer (if any) third-parties accessing the various APIs they provide, reducing the cost of support. It allows the information owner to concentrate on the key issues of ingest and maintenance of data. The provider also benefits where there is a Dataworks Enterprise-Related solution in place, in that it becomes easier to use that installation as a "trojan-horse" for additional data sales, even where the customer is new to the particular source in question.

Dataworks Enterprise is a "Distribution System"

Distribution System?

Dataworks Enterprise provides a set of standard components that allow you to distribute data between boxes in a number of different ways. Distribution is usually achieved using standard Dataworks Enterprise components using TCP/IP virtual circuits, although Dataworks Enterprise has other components to do this

The standard distribution components provide resiliency and fail-over, increasing the reliability of production systems.

Dataworks Enterprise is a "Dynamic Messaging System"

Messaging System?

Dataworks Enterprise provides a set of basic constructs that allow a client to make a request of a server and receive responses.  This forms the basis of the Dataworks Enterprise as a messaging system.

Dynamic?

A client can make requests to the server either for a single 'snapshot' of the data, or as a 'subscription' to the data. When the source data changes the Dataworks Enterprise dynamically pushes the updates to subscribing clients.

Dataworks Enterprise is "not a Database"

Not a database?

Although, Dataworks Enterprise can distribute data sourced from databases (indeed, there are standard Dataworks Enterprise components that allow you to do this) and can be used to populate databases, Dataworks Enterprise is not a database, except in the loosest possible sense of the term.

For instance, Dataworks Enterprise has no notion of a permanent on-disk repository of data as in a database. Dataworks Enterprise cache is based on memory. Dataworks Enterprise assumes that content is recoverable from the original provider, if necessary. Dataworks Enterprise is also not transactional in the sense that a database is.

Equally, the internal structures and data models of Dataworks Enterprise have some similarities to the internal structures of a database, but unlike a database, Dataworks Enterprise is designed to propagate large numbers of updates every second (in order to handle the trading volume of the leading markets).

It is better to think of Dataworks Enterprise as a Cache and a Messaging System rather than as a database.

Dataworks Enterprise is "not a Search Engine"

Not a Search Engine?

Although, Dataworks Enterprise can utilise search engines (indeed, Dataworks Enterprise News system does this), it is not essentially a search engine in its own right.

Dataworks Enterprise is "not a Concordance"

Not a Concordance?

Dataworks Enterprise can utilise concordance and name translation systems (and integrate them into Dataworks Enterprise using the "Resolution" component), however Dataworks Enterprise is not intrinsically a concordance in its own right.

Dataworks Enterprise has the "Easiest API" to use

Easiest API?

The standard Dataworks Enterprise API is one of the key reasons that the product is so successful.  The API is available to any "automation-capable" language including VB, C++ and VJ++. Web programmers can develop ASPs in VBScript and JScript using this API. Unix programmers have used the XML API into Dataworks Enterprise which utilises the same fundamental data model as the standard COM API. The Dataworks Enterprise' Real-time Web Kit (JRTClient), and the forthcoming 'JPress', also offer the same API, implemented in standard Java, which allows Java developers to get the full benefit of Dataworks Enterprise.

For instance, you can write a fully functioning data source in VB in about 20 lines of code and distribute the source across a network of machines. (We sometimes do this at demos, which tends to impress the customers. But then, don't take our word for it, try it).

Dataworks Enterprise is "Component-Based"

Component-Based?

One of the driving factors in the initial design of Dataworks Enterprise was to make a system that is component-based. Imagine, if you will, solutions that are constructed like Lego, i.e. out of a set of basic building blocks. This is how Dataworks Enterprise systems are designed. The standard components are installed and configured just like lego bricks. There are a number of corollaries of this:

Dataworks Enterprise Development Group owns no information

No information?

Dataworks Enterprise Development Group is a technology group, we do not have ownership of any datasets. We do not specialise in the collection and verification of information about the financial world, but in its integration and dissemination to customers.