Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
HD-Chapter:Architecture
Description
Created question in FIWARE Q/A platform on 23-02-2016 at 16:02
Please, ANSWER this question AT http://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).
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
1d 17h 53m | 1 | Manuel Escriche | 25/Feb/16 11:56 AM | |||||
|
6m 20s | 1 | Backlog Manager | 25/Feb/16 12:02 PM | |||||
|
1d 23h 59m | 1 | Backlog Manager | 27/Feb/16 12:02 PM |
Fix Version/s | 2021 [ 12600 ] |
Summary | FIWARE.Question.Tech.Best FIWare architecture? | FIWARE.Question.Tech.Architecture.Best FIWare architecture? |
Description |
Created question in FIWARE Q/A platform on 23-02-2016 at 16:02 {color: red}Please, ANSWER this question AT{color} http://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). |
Created question in FIWARE Q/A platform on 23-02-2016 at 16:02 {color: red}Please, ANSWER this question AT{color} http://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). |
HD-Chapter | Architecture [ 11000 ] |
Summary | [fiware-stackoverflow] Best FIWare architecture? | FIWARE.Question.Tech.Best FIWare architecture? |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Manuel Escriche [ mev ] |
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
2016-02-27 12:05|UPDATED status: transition Finish| # answers= 1, accepted answer= False