Lack of standards hinders adoption of M2M communications

Lack of standards hinders adoption of M2M communications

Date: Feb 07, 2014

The Internet of Things (IoT), or machine-to-machine communications (M2M), has struggled to gain traction in the enterprise. Confusion surrounding the benefits of M2M communications and a lack of standards is hindering adoption, according to Object Management Group CEO Richard Soley.

With standards organizations working together and focusing on various vertical markets, Soley predicts an uptick in use of M2M communications by enterprises down the road. "We are going to have to build standards that allow us to bridge at a very high level between systems, and we are going to not only have low-level standards for things like restful  APIs [application programming interfaces] and DDS [digital data storage] and other protocols and languages for integrating at the low level," he said.

Once M2M communications use becomes more widespread, developers will need to be prepared to integrate many different protocols, rather than dealing with a single API, protocol and network.

Watch the above video for more on what has stalled enterprises from embracing the IoT and what is being done to change that.

About the author:
Maxine Giza is the associate site editor for SearchSOA and can be reached at mgiza@techtarget.com.

Follow us on Twitter @SearchSOA and like us on Facebook.

More on Enterprise Application Integration (EAI)

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: