|
Time of Deployment and Integration
|
|
|
1-6 months
Building an application with a forex data feed requires project time for provisioning the feed, deploying data management infrastructure and coding data integration, storage and access.
|
< 1 day
On-demand forex data is immediately available over the Internet via Web services that require a few lines of code to integrate. Data is pulled directly into the application.
|
|
Total Cost of Ownership
|
|
Subscription
|
Feed and/or End Users
A forex data feed is generally sold in bulk based for a fixed feed price and additional end user fees, requiring the customer to buy additional data that is not used by every application or end user.
|
Web Service Requests
On-demand forex data is sold on a transaction basis that scales with the actual amount of data consumed; therefore there is no minimum data set or volume requirement to achieve a strong ROI.
|
|
Communications
|
Leased Line
A forex data feed is delivered via a leased line and requires additional network costs.
|
Internet
On-demand forex data is delivered over the Web and only requires a standard Internet connection.
|
|
Software
|
Data Management
A forex data feed requires additional software to parse, clean and access the data that must be provided by the vendor or coded by the customer.
|
None
On-demand forex data is accessed using pre-built Web service operations that are automatically imported into developer tools for immediate use.
|
|
Hardware
|
Data Storage
A forex data feed requires on-premise hardware to receive, store, process and provide access to data for end use in applications.
|
None
On-demand forex data is passed in real-time directly to the application in response to Web service requests. No local storage or hardware is required.
|
|
Flexibility of Future Modification
|
|
|
Software Configuration and Coding
When using a forex data feed, flexibility is determined by the vendor’s add-on software applications. Data access that is not configurable must be coded by the customer.
|
Web Service Operations and Mashups
On-demand forex data is delivered using Web services with many pre-built operations. In addition, new operations can be easily created using the Splice mash-up platform.
|
|
Volume
|
|
|
In-house Infrastructure Scalability
When using a forex data feed volume requirements must be handled by the customer’s on-premise IT infrastructure and impact the requisite up-front investment and lead time for deployment.
|
Cloud Computing Scalability
On-demand forex data is available for any volume level. Xignite handles billions of service requests per month and employs Amazon elastic cloud computing (EC2) for very high volume applications.
|
|
Latency
|
|
|
< 1 msec Feed/In-House Dependent
Overall latency when using a forex data feed is determined by the network and the customer’s IT infrastructure. Very low latency applications require colocation access and very high speed processing.
|
< 100 msec Cloud/Internet Dependent
Latency of on-demand forex data is determined by the cloud service providers system and the request-response time of the Internet. Latency of a typical Xignite Web service is several hundred milliseconds, but can vary based on the customer’s Internet access.
|
|
Availability
|
|
|
> 99% Feed/In-house Dependent
When using a forex data feed, availability is a combination of the vendor’s feed and the customer’s software and hardware infrastructure. In-house infrastructure must be built to handle peak volume levels.
|
> 99% Cloud/Internet Dependent
On-demand forex data availability is guaranteed by the vendor’s service level agreement (SLA) and is based on enterprise-class infrastructure that must be capable of handling the volume of all customers.
|