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 : [email protected] Mobile : +94716007376 <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
