Poll results: Essential (Java) technologies for IoT
In our recent poll we asked for your opinion regarding essential (Java) technologies for the ‘Internet of Things’. About 300 voters casted their votes, the percentage distribution is displayed below, please note that multiple responses were possible:
We had called on the community to vote, here in our blog and at the German Java conference JAX in Mainz. Thanks to all voters for mirroring their opinions!
Congratulations to the winner of the Bosch Power Box at the JAX conference with 360° surround sound. Enjoy! 🙂
Here, we introduced our activities in the fields of the ‘Internet of Things’ in last year´s poll. Of course we continued our development bringing in our rule-based concepts and technologies. By doing this we are facing a considerably huge technology stack and asked for your perception of some of the technologies. Please find out how they are linked to our platforms and technologies for the ‘Internet of Things’ in the following:
The OSGi specifications allow multiple Java based components to efficiently cooperate in a single Java Virtual Machine (JVM) and provides an extensive security model so that components can run in a shielded environment. Read more: http://www.osgi.org
Visual Rules integrates well with the OSGi Framework, e.g. rules are available as OSGi bundles. The Visual Rules Suite supports and consumes OSGi services as well.
Radio-frequency identification (RFID) uses radio waves to exchange data between a reader and an electronic tag attached to an object, for the purpose of identification and tracking. Near field communication (NFC) is a set of short-range wireless technologies, typically requiring a distance of 4 cm or less. Read more: http://en.wikipedia.org/wiki/Radio-frequency_identification and: http://en.wikipedia.org/wiki/Near_field_communication
We are using RFID technology for example in our eMobility charging infrastructure for authentification purposes. RFID signals or events can trigger state transitions and downstream rules processing within Visual Rules state flow models.
The most common interpretation of NoSQL is “non-relational” and emphasizes the advantages of Key-Value Stores, Document Databases, and Graph Databases. Read more: http://en.wikipedia.org/wiki/NoSQL
Our platform for the internet of things is able to use NoSQL data like many other data sources.
The Java Management Extensions (JMX) API typically includes consulting and changing application configuration, accumulating and publishing statistics about application behavior, as well as notifying users or applications of state changes and erroneous conditions. Read more: http://openjdk.java.net/groups/jmx/
Our platform will be using JMX for the remote management of things within these kind of massively distributed applications. The support of JMX is currently on the platform´s development roadmap.
Java Platform, Micro Edition (Java ME) provides a robust, flexible environment for applications running on mobile and other embedded devices. Read more: http://www.oracle.com/
Visual Rules rule packages can be flexibly scaled to a size which is executable on small devices. However, the support of Java ME is currently not pursued, as our hardware component which connects the ‘Things’ world to the ‘Enterprise Application’ world is powerful enough to be Java EE 6-compliant.
ZigBee supports interoperable standards including ZigBee Health Care, ZigBee Home Automation, ZigBee Smart Energy, ZigBee Telecom Services, and the forthcoming ZigBee Building Automation and ZigBee Retail Services.
ZigBee offers a variety of sensors and actuators which can be wirelessly connected with Visual Rules Suite components and our internet of things platform as well. Visual Rules is able to process emerging sensor data and trigger actuating elements as a consequence.
Thanks again for all your votes. I am really happy, so many of you shared your thoughts on this. All questions and comments on the ‘new’ technologies are still highly appreciated, just drop a few lines in the text box below. 🙂