*First, my definition of a (micro) G/W* - connection point between the cloud, service impls, sensors, etc - all data movements happen through it - supports various transports / protocols - deals with security - ability to shadow/access throttle endpoints behind it - cloud server provides the holistic view of all (micro) G/W deployments - provides external integration points via APIs
We have following options now. *Micro API G/W* We have a micro API G/W doing pretty much of above capabilities. But AFAIK it lacks following. - limited transport support (only support HTTP and websockets) - no streaming/event receiving support *Siddhi runtime:* - consist of input/output adaptors covering vast transports/protocols. - streaming / event processing capabilities But with not much of build in support for - exposing APIs - security verifications We are trying to rethink IoT G/W part within IoT Server to support APIs, events and Streams. Right now it is built around C4 based API G/W, hence supporting HTTP only. So wondering what is the correct path to take... --- Sumedha Rubasinghe Director - IoT Architecture, WSO2 m: +94 773017743
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
