michael's profile - activity

I posted this question on StackOverflow as well, http://stackoverflow.com/questions/33.... No answer there yet so I'm posting here as well.

I am to design an IOT platform which should collect sensor data from tens of thousands of sources or more. Process this data in different ways and present the user with interactive dashboards which allow the user to drill down through the aggregate information down to the specific device level. Also support the case where the user might ask for live information from that specific device.

I have ideas which tools I could use for data stream distributed processing but not much about how to interface with IOT devices. And that's why I started looking into FIWARE.

Reading through FIWARE site, different FIWARE architecture documents, GE specific documentation etc. and trying to answer my own design architecture questions. The abundance of available information is confusing to say the least. I think that my main difficulty at the moment is to map from the architecture as it is described here to the actual available implementation components.

Question: If I am to use FIWARE GEis as a device proxy which receives data from devices and forwards to the realtime processing pipeline, which GEis should I use? And which specific implementations?

Thanks! Will update..

I'm new to FIWARE and still reading and trying to wrap my head around the architecture. My use case involves hundreds of thousands of events per second, where I'm thinking of leveraging FIWARE to collect sensor data and then forward to our data processing/cep platform. I've read that Orion depends on MongoDB for state management. So my questions is whether Orion scales horizontally and whether it's able to handle five or six figures of events per second?