[Backlogmanager] [FIWARE-JIRA] (HELP-13296) [fiware-stackoverflow] Best FIWare architecture?

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez deleted HELP-13296:
----------------------------------


> [fiware-stackoverflow] Best FIWare architecture?
> ------------------------------------------------
>
>                 Key: HELP-13296
>                 URL: https://jira.fiware.org/browse/HELP-13296
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>              Labels: fiware, fiware-cosmos, fiware-cygnus, fiware-orion, fiware-wirecloud
>
> Created question in FIWARE Q/A platform on 23-02-2016 at 16:02
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/35581026/best-fiware-architecture
> +Question:+
> Best FIWare architecture?
> +Description:+
> We are developing a FiWare city sensor network that:
> Inside the sensor processes data in real time and publishes their average every N minutes to our server;
> some server side math to do with those reported averages, which will generate new fields or averages of already reported fields (e.g. average by day);
> In the end, there will be a Wirecloud component showing a map with the location of every sensor and a plot showing the several fields acquired, by sensor.
> Aditionally, sensors can raise alarms and every server and sensor access must be secure and server database scalability it's a future concern. At the moment we have this architecture (OCB stands for Orion Context Broker):
> Where the "Webservice" and "Processing" components are house made, but after reading a little bit more about FIWare components (particulary the IOT stack) I've realised that there are more components that we might integrate in here.
> What are you using for a solution like this? It looks fairly generic (secure attributes publish, storage, post-processing and value plot).



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)