Revolutionizing Retail With IoT for Omnichannel Success

Think about the last thing you bought. How important was technology to the purchase process? Perhaps you did some research online to compare specs or prices, before buying in store. But, more likely than not, a traditional brick and mortar store didn’t factor into your decision at all. More and more purchases today are taking place online, or increasingly from directly within a retailer’s mobile app. Let’s think about how that changes the customer relationship and the role of the retailer in our societies.

When the web and mobile technologies first became accessible to retailers, they invested significant time and resources to drive consumers to these channels. Technology attempted to make online purchases as seamless as possible and to recreate the in-store experience online. Ironically, traditional retailers now face the opposite problem: attempting to drive traffic back into stores by providing an experience that surpasses the convenience and breadth of the online marketplace. https://goo.gl/gZmHA7 #DataIntegration #ML

REST and gRPC Side-by-Side in New Google Endpoints Documentation

ICYDK: Google has been really moving forward with their development, and storytelling around gRPC. Their high speed to approach to doing APIs that uses HTTP/2 as a transport, and protocol buffers (ProtoBuf) as its serialized message format. Even with all this motion forward they aren’t leaving everyone doing basic web APIs behind, and are actively supporting both approaches across all new Google APIs, as well as in their services and tooling for deploying APIs in the Google Cloud – supporting two-speed APIs side-by-side, across their platform.

When you are using Google Cloud Endpoints to deploy and manage your APIs, you can choose to offer a more RESTful edition, as well as a more advanced gRPC edition. They’ve continued to support this approach across their service features, and tooling, by now also documenting your APIs. As part of their rollout of a supporting API portal and documentation for your Google Cloud Endpoints, you can automatically document both flavors of your APIs. Making a strong case for considering to offer both types of APIs, depending on the types of use cases you are looking to solve, and the types of developers you are catering to. https://goo.gl/Tkuo1H #DataIntegration #ML