What does the developer need for the internet of things?

"Editor's note" is considered to be the next tuyere in the field of Internet of things, bringing together a large number of hardware and software manufacturers to join the competition, Cisco, Dell, IBM, At&t, Verizon, Oracle, Intel and even GE are all in the layout, they or the introduction of their own things networking system, or collaborate to form alliances that want their systems to be standard, but what do they need as developers?

The following is the translation:

Nowadays, many companies are interested in the Internet of things, although the internet market is very confusing, but today's technology giants are racing to change it. Most manufacturers believe that the internet of things is an opportunity for system integration and a magic box that collects the organization's GB data on thousands of sensors.

Cisco, Dell, IBM, At&t, Verizon, Oracle, Intel and even GE are trying to build some version of physical hardware or software for sale. Some of these companies have even teamed up with the Industrial Internet Alliance (Industrial Internet Consortium) to try to build a reference architecture so that other vendors can simply plug in the hardware design and business processes available so they can take advantage of cheap sensors and make connections simpler and easier.

But this approach attempts to make the internet of things conform to expensive machine-to-machine models, but in a world of open source software, the choice of cheaper connectivity and agile design cycles is not far off.

The IoT needs developers, and the developers need tools. The key is not the device, but the data generated by these devices and the applications built on it. But developers use the data generated by the IoT, which is still an open issue because of the pros and cons, but it is possible for developers to build programs on these data if we can really take advantage of the possibilities mentioned in the Bosch article.

When applications are dramatically modular, a specific technology model can be reused from one application to another, and an exciting area of application development will open up. This may involve interfaces to the connection layer, data analysis tools, deep embedded rule engines or security components, and even database options and cloud services. From an application designed to measure water levels for a container, and is there a specific module that can be reused by other applications and as part of a "software as a service" product? Mash-up application is already one of Thingworx success stories, perhaps the next possible development will be to build a library or application repository for basic application mash-up? Is this the SDK for the internet of things?

This may seem obvious, but it is not obvious what tools the developers of the great apps developed on the Internet are looking for. The Bosch article mentions xively, Axeda, and so on, but it looks more like storing data and providing APIs for it. Now, many companies are selling platforms that allow developers to transition from arm mbed to Cisco's Devnet or IBM's new IoT Foundation. Others offer agreements such as the Eclipse Foundation's MQTT or Intel-supported Openinterconnection Consortium, and some are selling APIs.

Original link: The Internet of things needs developers. So what do developers need? (Zebian/Wei)

Free Subscription "CSDN cloud Computing (left) and csdn large data (right)" micro-letter public number, real-time grasp of first-hand cloud news, to understand the latest big data progress!

CSDN publishes related cloud computing information, such as virtualization, Docker, OpenStack, Cloudstack, and data centers, sharing Hadoop, Spark, Nosql/newsql, HBase, Impala, memory calculations, stream computing, Machine learning and intelligent algorithms and other related large data views, providing cloud computing and large data technology, platform, practice and industry information services.