What Should I Use (Notification/Events) To Send Data From Application Server To End Points (Devices) and vice versa Using KAA Middleware -

as per kaa references, understand once should use notification feature, when required send data server (external apps) endpoints , events used when there need endpoint endpoint communication (kind of device binding requirement)

so, achieve request/response functionality using kaa. need implement hybrid solutions below.

1) in server, can run 1 kaa sdk instance , use event feature request endpoint , response endpoint.

or

2) server, use notification rest api request , response through data logger feature using in-build appender configuring "loguploadstrategy" uploads every log record created.

notes point 1

• as per andrew, solutions architect of kaa iot platform

  "you can embed sdk standalone application , host in on same server kaa-node present. application may receive rest api calls , forward them particular endpoints via kaa events feature. however, useful test purposes. not recommend solution in production because hard scale , has potential security issues"

notes point 2

• it satisfies kaa reference document andrew's suggestion request how can achieve response.

questions point 1

1) causes scale application , type of security issues faces through uses rsa 2048 encryption communication?

2) can embed more 1 sdk in standalone application , host in on same server kaa-node present.

questions point 2

3) if device sends notification response along telemetry data, can increase latency , other performance issue.

common questions

4) 1 better approach achieve request/response functionality?

any or suggestion appreciated.

1) causes scale application , type of security issues faces though uses rsa 2048 encryption communication?

it makes ep on server side single point of failure , not allow load balancing. security issues, andrew meant: this application may receive rest api calls , forces 1 provide additional security rest api calls , better use first hybrid solutions using solely event feature.

2) can embed more 1 sdk in standalone application , host in on same server kaa-node present.

no, can't use more 1 sdk in 1 application, can run couple of instance on 1 machine in different directories in order prevent collisions of autogenerated security keys , other files.

3) if device sends notification response along telemetry data, can increase latency , other performance issue.

of course, face delays if start sending , big portions of data on both sides. if have lot of devices sends in total big amount of telemetry data, can increase performance on server side start-up kaa in cluster mode or add new nodes processing requests.

4) 1 better approach achieve request/response functionality?

the second hybrid solution – data collection , notification features. doesn't cause problem scale , can launch kaa server in cluster mode.