Petabyte

Messaging for the Internet of Things   As we embed processing power to a lot of our everyday things. The thing will need to communicate with a server to send data or get data . The thing needs data in order to make something happen. The thing needs to send data so that we can be smarter on how we use the thing. But How do we send data to a central server that is robust, asynchronous and reliable ? MQ, what is old is new Again  MQ or Message Qeueing is new again in the age of the Internet of Things. Messaging Patterns for the enterprise has been around for ages. What were the major reasons that messaging addresses ? 1. Networks are unreliable - data needs to be transported over the network. These networks are a conglemeration of different types of network. Since we do not have control of over most of the network that we use to access the internet. The network will present a lot of problem specially when you are sending messages across the internet. 2. Networks are slow - The

A decade of Ajax About 10 years ago the Ajax word was coined to describe the interactive  web that Google created at that time Google Suggest and Google Maps  ( Ajax - Jesse James )  . At the heart of that emerging technology is a Microsoft created object XHR(XMLHttpRequest - XMLHttpRequest ) and is now adopted by Mozilla, Apple, and Google (IE is a different Web technology story). XHR is now being adopted as a standard in W3C ( standardized XHR - W3C ). But not only that there is XHR2 ( HTML5 Rocks )  - (I think this has been discontinued.) XHR provides an easy way to retrieve data without doing a page refresh. Despite its name we are using XHR for any structured data that the server can provide us. (JSON, JSON-LD) - and binary data ( SPDY HTTP 2.0 ) We have used AJAX in a lot of creative  (SPA, Web API, MashUps) ways and I am excited to see the next decade of highly interactive web designs. The Future What would the role of AJAX be in the internet of things ? M