Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4233

FIWARE.Question.Tech.IoT.IDAS.Why FIWARE IoT exists when we already have solutions such as IoTSYS, Domotic OSGi Gateway, openHAB and others?

    Details

      Description

      Created in FIWARE Q/A platform on 02-07-2015 at 23:07
      Answer this issue at http://stackoverflow.com/questions/31195251/why-fiware-iot-exists-when-we-already-have-solutions-such-as-iotsys-domotic-osg

      Question:
      Why FIWARE IoT exists when we already have solutions such as IoTSYS, Domotic OSGi Gateway, openHAB and others?
      Description:
      First of all I have to admit that I find the FIWARE project very interesting and it really targets the current technological needs the world is facing at the moment.

      However, I believe that some FIWARE components could use already existing solutions instead of reinventing what already exists for some time. If you look closely you will see that, aside from the names given to equivalent concepts, FIWARE Architecture is very similar to the ones I mention in the title. Not that FIWARE is ripping off ideas, it is just that these things already exist and the final solutions are very similar.

      Moreover, the main problem is that there are as many solutions to solve the IoT hardware heterogeneity problem as devices they try to integrate. In the end, creating more integration frameworks and standards will solve no problem at all, it will aggravate it even further by spreading manufacturers and developers attention to several means of integration, mitigating the purpose of integration frameworks and standards!

      First we had BACnet/WS, OPC DA, oBIX etc. Then we had UPnP, CoAP and 6LoWPAN. After there were DOG, openHAB and IoTSYS. Now we have FIWARE and AllJoyn! Please we have to find another way to solve this severe issue.

      OR is there a reason that I am unaware justifying the creation of another integration framework?

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        5d 2h 36m 1 Carlos Ralli Ucendo 23/Sep/15 6:01 PM
        In Progress In Progress Answered Answered
        2s 1 Carlos Ralli Ucendo 23/Sep/15 6:01 PM
        Answered Answered Closed Closed
        1s 1 Carlos Ralli Ucendo 23/Sep/15 6:01 PM

          People

          • Assignee:
            ralli Carlos Ralli Ucendo
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: