Stream computing features
Real-time analytic processing (RTAP)
Uses RTAP, which extends online analytic processing (OLAP) by analyzing data-in-motion, instead of data-at-rest. This enables higher volume and lower-latency analysis. It is characterized by high throughput rates of disparate data types, including structured and unstructured information, that can be processed with millisecond or microsecond latencies using complex correlations and powerful analytics.
Multiple, heterogeneous data streams
Processes data streams that originate from any of the following: IoT devices and sensors; text files, spreadsheets, images, video and audio recordings; email, chat and instant messaging; web traffic, blogs and social networking sites; financial transactions, customer service records, telephone usage records, and system and application logs; as well as satellite data, GPS data, smart devices, sensors, network traffic and messages.
Support for Apache Edgent
Allows you to create federated applications to optimize computing for IoT applications, with Edgent at the edge and Streams for central analytics. Communications can be performed natively with Streams or using a management service such as the IBM Watson IoT platform on IBM Bluemix.
Enables developers to create applications that ingest voice, convert it to text and perform natural language processing. Designed for mobile experiences, transcribing media files, call center transcriptions, voice control of embedded systems or converting sound to text, enabling data to be searchable.
RedHat Enterprise Linux (RHEL) 6.x or 7.x for 64-bit x86 architecture hardware
RHEL 6.x or7.x for 64-bit POWER7/POWER8 architecture hardware
- SLES does not support SELinux
- Eclipse Platform SDK V4.2.2
- IBM SDK Java Technology Edition V7 for x86/POWER7 architecture hardware
- Oracle Java SE V7.0 SDK for x86 architecture hardware
- Mozilla Firefox 10/ later
- Microsoft IE 9/ later
x86 architecture (64 bit)/ IBM POWER7/POWER8 architecture server with a minimum of 2 GB memory to run simple applications, such as the Commodity Purchasing Sample For Hyperstate Accelerator, separate x86 architecture (64 bit)/POWER8 architecture server is required with a minimum of 8 GB memory.For persistence, Hyperstate Accelerator requires an IBM FlashSystem 840/FlashSystem 900 storage system