Unknown macro: {next_previous_links}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

WSO2 Data Analytics Server 3.0.0 combines real-time, batch, interactive, and predictive (via machine learning) analysis of data into one integrated platform to support the multiple demands of Internet of Things (IoT) solutions, as well as mobile and Web apps as illustrated by the image below.

types of analytics supported by WSO2 DAS

 

As a part of WSO2’s analytics platform, WSO2 DAS introduces a single solution with the ability to build systems and applications that collect and analyze both realtime and persisted, data and communicate the results. It is designed to treat millions of events per second, and is therefore capable to handle Big Data volumes and Internet of Things projects.

WSO2 DAS 3.0.0 workflow consists of the following three main phases.

Aggregating data

WSO2 DAS exposes a single API for external data sources to publish data events to it. Further, it provides configurable options either to process the data event stream inflow (in memory) for realtime analytics, to persist (in data storage) for batch analytics and/or to index for interactive analytics as shown in the below diagram.

aggregating data

Creating event streams

The first step in aggregating data is defining an event stream by creating the event stream definition. A stream definition provides the initial structure and identification required for event processing. It includes a set of data types as properties, name, version and other attributes. When  an external data publisher sends data events to WSO2 DAS (the receiver), it needs to specify the name and version of the stream intended. Also, data events should be sent according to the structure defined in the stream definition. For more information on event streams, see Event Streams.

Persisting events

WSO2 DAS introduces a pluggable architecture which allows you to persist data events into any relational data storage (i.e. Oracle, MSSQL, MySQL etc.), or NoSQL storage (i.e. Apache HBase, Apache Cassandra etc.). It is also possible for multi data event storage. For an example, the events can be stored in a NoSQL storage while the processed data events can be stored in a relational data storage.

Creating event receivers

Event Receivers are the connectors to different data sources in WSO2 DAS. WSO2 DAS support s event retrieval from many transport protocols and different formats. For information on the supported transport protocols and event formats, see Event Receiver Types.

Analyzing data

You can configure any data event stream received by WSO2 DAS or batch and/or real time analytics.

Batch analytics

You can perform batch analytics when you configure and persist event streams for batch processing scenarios such as data aggregation, summarization etc. WSO2 DAS batch analytics engine is powered by Apache Spark, which accesses the underlying data storage and executes programs to process the event data. An SQL-like query language is provided to create the jobs that needs to be executed. For more information, see Data Analysis.

Realtime analytics

You can process the event streams inflow through the  WSO2 real time analytics engine which is powered by Siddhi. For this, you need to specify a set of queries or rules using the SQL like Siddhi Query Language. The realtime analytic engine can process multiple event streams in realtime. For more information see, Working with Execution Plans.


  • No labels