[prev in list] [next in list] [prev in thread] [next in thread]
List: esb-java-dev
Subject: [Dev] Siddhi Cloud Native Strategy Proposed Design
From: Chiran Fernando <chiran () wso2 ! com>
Date: 2019-03-27 15:48:48
Message-ID: CABNeXEg8jEWdbE13FTSn-DjTq1ts9=zTYk7r2tWa3UkLs-5ZCg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all,
Siddhi already has a traction as a open source stream processing library,
we are leveraging that edge to pitch Siddhi as a cloud native stream
processing engine.
The proposed experience would be based on the *operator pattern* and will
make use of the Operator SDK
<https://github.com/operator-framework/operator-sdk> to perform operations
on Kubernetes resources.
We'll be creating a kubernetes custom resource(CRD) for the Siddhi
deployment.
The operator will be written in Go and the Siddhi runtime would be a JVM.
In order to identify the needed specifications, I focused on the below
Siddhi deployments.
1. Siddhi stateless/default deployment
2. Siddhi stasteful deployment
3. Siddhi fault tolerance deployment
4. Siddhi distributed deployment
I created and deployed Kubernetes artifacts manually for these deployments
separately. Thereafter analysed the manually created artifacts to create
the proposed CRDs.
We had a discussion to review the design for the CRDs. Please find the
design document and the meeting recording in [1] and [2] receptively.
We highly appreciate everyone to go through the meeting and the design
document and share your feedback and suggestions in this regard.
[1]
https://docs.google.com/document/d/1Dniw-Htc6ZqcXyigxEnC1Ia3FX6GDPDsBLV81OBVmCo/edit?usp=sharing
[2]
https://wso2.zoom.us/recording/play/aW9EIfPyeaE0sdpcUEHBAIADB2gNb2c_DexERNu2Tffd1GuyijBNHX527PZnWB4R?continueMode=true
--
*Chiran Fernando*
Senior Software Engineer | WSO2
Email : chiran@wso2.com
Mobile : +94716007376
<http://wso2.com/signature>
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div \
dir="ltr"><div dir="ltr"><div dir="ltr">Hi all,<div><br></div><div>Siddhi already has \
a traction as a open source stream processing library, we are leveraging that edge to \
pitch Siddhi as a cloud native stream processing \
engine.<br></div><div><br></div><div>The proposed experience would be based on the \
<i><b>operator pattern</b></i> and will make use of the <a \
href="https://github.com/operator-framework/operator-sdk" target="_blank">Operator \
SDK</a> to perform operations on Kubernetes resources.</div><div>We'll be \
creating a kubernetes custom resource(CRD) for the Siddhi deployment.</div><div>The \
operator will be written in Go and the Siddhi runtime would be a \
JVM.</div><div><br></div><div><img \
src="https://lh6.googleusercontent.com/rIrNnKwVALZ3H_hu3gW4wOnx32ueAtIeK9PRA5-WI9-66SE \
EVbjWZRZLEVP2fhPKoiJSrxGs7XqP7TlNDoH7vTQxMNjl2P0zc9aI7S7fUPQ06OAxfGAeS6t3-5YaB7axBRzXys51tFg" \
width="760px;" height="415px;"><br></div><div><br></div><div>In order to identify the \
needed specifications, I focused on the below Siddhi \
deployments.</div><div><ol><li>Siddhi stateless/default deployment</li><li>Siddhi \
stasteful deployment</li><li>Siddhi fault tolerance deployment</li><li>Siddhi \
distributed deployment</li></ol></div><div>I created and deployed Kubernetes \
artifacts manually for these deployments separately. Thereafter analysed the manually \
created artifacts to create the proposed CRDs.</div><div><br></div><div>We had a \
discussion to review the design for the CRDs. Please find the design document and the \
meeting recording in [1] and [2] receptively.</div><div><br></div><div>We highly \
appreciate everyone to go through the meeting and the design document and share your \
feedback and suggestions in this regard.</div><div><br><div>[1] <a \
href="https://docs.google.com/document/d/1Dniw-Htc6ZqcXyigxEnC1Ia3FX6GDPDsBLV81OBVmCo/edit?usp=sharing" \
target="_blank">https://docs.google.com/document/d/1Dniw-Htc6ZqcXyigxEnC1Ia3FX6GDPDsBLV81OBVmCo/edit?usp=sharing</a></div><div>[2] \
<a href="https://wso2.zoom.us/recording/play/aW9EIfPyeaE0sdpcUEHBAIADB2gNb2c_DexERNu2Tffd1GuyijBNHX527PZnWB4R?continueMode=true" \
target="_blank">https://wso2.zoom.us/recording/play/aW9EIfPyeaE0sdpcUEHBAIADB2gNb2c_DexERNu2Tffd1GuyijBNHX527PZnWB4R?continueMode=true</a></div><div>-- \
<br></div></div></div></div></div></div></div></div><div dir="ltr" \
class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div \
dir="ltr"><div><div dir="ltr"><b>Chiran Fernando</b><div><font size="2">Senior \
Software Engineer | WSO2</font></div><div><font size="1"><br></font></div><div><font \
size="2">Email : <a href="mailto:chiran@wso2.com" \
target="_blank">chiran@wso2.com</a></font></div><div><font size="2">Mobile : \
+94716007376</font></div><div><font size="2"><br></font></div><div><font size="2"><a \
href="http://wso2.com/signature" target="_blank"><img \
src="http://c.content.wso2.com/signatures/wso2-signature-general.png"></a><br></font></div></div></div></div></div></div></div></div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic