Hi,
Thank you for the feed backs. So our implementation approach will be BAM
pre-calculates a historical view of the system using hive queries and CEP
calculates the most recent view of the system using siddhi queries. The
service layer which will be a CEP Event table (RDBMS table) responsible for
Hi,
On Thu, Nov 27, 2014 at 6:36 PM, Inosh Goonewardena wrote:
> Hi,
>
> On Thu, Nov 27, 2014 at 4:34 PM, Maninda Edirisooriya
> wrote:
>
>> This seems nice. But I am not sure how the precomputation works and how
>> the intermediate indexes are stored in Service Layer.
>>
>
> Basically the idea
Hi,
On Thu, Nov 27, 2014 at 4:34 PM, Maninda Edirisooriya
wrote:
> This seems nice. But I am not sure how the precomputation works and how
> the intermediate indexes are stored in Service Layer.
>
Basically the idea should be to store outputs from both batch and speed
layers in the serving laye
This is much cleaner approach to utilize both the features of BAM and CEP.
Since the components for Batch layer and Speed layer are already
implemented, it just need to get them properly placed. So the major concern
is serving layer. IMO serving layer should provide drill down and data
manipulation
This seems nice. But I am not sure how the precomputation works and how the
intermediate indexes are stored in Service Layer.
And also does the user have to write both hive scripts and Siddhi queries
for the same scenario?
Thanks.
*Maninda Edirisooriya*
Senior Software Engineer
*WSO2, Inc.*lean
Hi all,
Myself with Zamly (za...@wso2.com) and Inshaf (ins...@wso2.com) are going
to develop $subject as described below.
*Introduction to Lambda architecture*
The lambda architecture solves the problem of computing arbitrary functions
on arbitrary data in real time by decomposing the problem int
