Using Java and Standards for Fast IoT Development [CON5513]

@leomrlima#FastIoTJ1

Using Java and Standards for Fast IoT Development [CON5513]

Leonardo Lima@leomrlima http://v2com.mobi


About meLeonardo Lima

•Computer engineer, server & embedded SW developer•From São Paulo, Brasil, now in Austin, TX•CTO at

•Spec Lead – JSR363•V2COM’s Representative at JCP Executive Committee

[www.linkedin.com/in/leomrlima]


AgendaAspects of IoT developmentBusiness & Technical Concerns (or Functional & Non Functional Requirements)Why Java?Using Standards – pick your flavor!IRLQ&A


ASPECTS OF IOT DEVELOPMENTOh so many things to consider!


IoT Development…Is not just connecting things

Has a lot of constraints

Has many horizontal aspects and as many vertical aspects


On connecting thingsThe buzz of IoT is connecting things

Does everything needs to be connected?

The implications of connectivity


It’s here and thereWe can talk about these concerns both in embedded and cloud development

We’re going to focus more on embedded


So many constraints!Hardware constraintsSoftware constraintsProtocol constraintsReal life considerations


Aspects deep and wide Business considerations• What process are we replacing, enhancing or

creating?• Who’s being impacted, equipment and people

wise?Technical considerations• Even very different verticals have the same

technical requirements – and this lets us leverage standards


BUSINESS & TECHNICAL CONCERNS (OR FUNCTIONAL & NON FUNCTIONAL

REQUIREMENTS)

What do you need, commander?


It starts very simple”Just need this value in this system”

”Can’t you just connect a cable and read it?”

”Just put a chip in there and it’ll work”

”But it’s just a modem”


But it gets complicatedExplicit concerns

And ones they don’t even think about


It gets down to• Safety• Security, Trust & Privacy • Resilience • Integrability, Interoperability and Composability • Connectivity • Data Management • Analytics and Advanced Data Processing• Device Management


WHY JAVA?would you like a cup of java with that, sir?


Java……is a programming language and computing platform first released by Sun Microsystems in 1995. …has a vibrant ecosystem where open source plays a major role…virtual machine allows true ”write once, compile once and run anywhere” for embedded and server environments


USING STANDARDS – PICK YOUR FLAVOR!Oh so many choices!


Standards address common issuesEvery major concern in our bucket list has at least one standard to address it

But sometimes too many standards do get in the way

Standards and open source go very well together


Data Management • Query, Publish and Subscribe

• Storage, Persistence and Retrieval

• Integration

• Description and Presence

• Rights Management


Security, Trust & Privacy • Endpoint security

• Communication security between the endpoints

• Data distribution and secure storage

• Management and monitoring security of both the endpoints and the communication mechanism


Connectivity• Communication Transport • Get data there

• Connectivity Framework • How data is structured and used


Integrability, Interoperability and Composability • Integrability

• Interoperability

• Composability


Device Management

• Day-to-day operations (who’s not online and why)

• Firmware & configuration management

• Billing

• Non-functional aspects


IRL (IN REAL LIFE)What would you choose?


A Smart Freezer

• ”Simple” business concept• Monitor temperature to avoid product loss

• ”Since we are doing this, why not…”• Monitor stock level• Check if others are using our freezer for something

else

• Server and embedded development


Addressing the concerns – Connectivity & Security• Use JCA (Java Crytography Architecture) for security

concerns• Or, alternatively BouncyCastle framework

• JavaCard/PKCS11 helps with authentication and cryptography

• Standard protocols for IoT communication• HTTPS (TLS/SSL) if you can afford• MQTT• CoAP


Addressing the concerns – Data Integration

• Java has plenty of standards for data parsing and representation

• JSR 363 for measurements• JSR 353 for JSON-P • JSR 339 for JAX-RS (REST)• JSR 343 for Messaging (JMS 2.0)• You can use an MQ that exposes MQTT to the devices and

JMS to your servers

• Using these standards in a Java EE environment will lead to a very efficient development


Addressing the concerns – Integrability

• Extensive Java EE standards for REST and SOAP WebServices

• JSR 363 helps with interoperability between diverse systems


It gets more complicated...

• When thinking of expansion, it does get more complicated as there are many different aspects to consider• Device management• Multiple WANs• Multiple legacy protocols

• There are plenty of options that encapsulate (some) of these concerns, for a cost (or not)


Going the open source route…

• iot.Eclipse.org has a ever increasing (20+) suite of tools and frameworks for IoT that helps to address some concerns we discussed• You can get professional support on top of them

• Kura (OSGi for services gateways)• Paho (open-source implementations of open and

standard messaging protocols)

• For server side, we get a LOT of options (just look at your session catalog )


… Or closed systems

• Major IT vendors have something to offer in IoT now

• For device development• Standard framework for development• Tight integration with backend system

• And server side• Device management• Message Routing• Analytics and Processing


Major IoT offerings

• Oracle IoT CS• IBM BlueMix• GE Predix• Microsoft Azure IoT• Amazon AWS IoT• PTC ThingWorx


Q & A


In the end…

• There are plenty of options to match plenty of requirements

• Each project is a project, and you’ll be re-evaluating requirements for each of them

• It pays to have a broad knowledge of what’s available and do a quick survey of their strengths

• Standardized solutions will always be the ones with better support and odds of being the best tool


Thanks!

Technology

Using Java and Standards for Fast IoT Development [CON5513]