Comments on: The Makeup of an M2M Network Architecture

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Sun, 26 Jan 2014 06:31:15 +0000

Rik,

I think each of the 3 “components” I mentioned can be packed into a specific device. You can have all 3 bunched together, you can have the decision making alone happen on a smartphone or in the cloud, you can have aggregation done closer to the devices.

And yes, you are correct – making a decision and enacting upon it can and should be separated.

As for Rainbows End – I am glad you like it.

By: Rik Harris

Rik Harris — Sun, 26 Jan 2014 06:21:07 +0000

In reply to Rik Harris. Oh, and thanks for the recommendation on Rainbows End. I enjoyed his earlier books and am currently enjoying this one :-)

By: Rik Harris

Rik Harris — Sun, 26 Jan 2014 05:20:07 +0000

It seems to me that there is an architectural difference between making a decision and enacting the decision. Getting the decision back into the real world to perform an action may be via the same devices that produce the data in the first place (like Nest) but not necessarily.

What do you think?

By: Chris Matthieu

Chris Matthieu — Mon, 20 Jan 2014 15:27:18 +0000

Nice post. There is definitely a link between WebRTC and the Internet of Things. I’ve recently shifted my development efforts from Twelephone (http://twelephone.com) to Skynet (http://skynet.im), an open source machine-to-machine instant messaging platform.

My new plan is to rewrite Twelephone to run on top of Skynet so that it handles all of the signaling and messaging between users. There’s no reason why people can’t have UUIDs like the machines connected to Skynet and perhaps communicate with them too on the same network. Industry experts are starting the call this idea the Internet of Everything.

Now I just need to figure out how to leverage the WebRTC data channel for M2M communications 😉