The Google Cloud Ruby SDK by Chris Smith interacts with the cloud storage features of the API, in addition to the data services of Google Cloud Datastore, DNS, PubSub, and Engine APIs. The aim is to save and retrieve any amount of data in a safe way from any part of the world. To learn more about what the API can do for a project, visit https://cloud.google.com/storage/docs/overview
Vonage has announced new functionality for their Verify API that aims to streamline the authentication workflow for the company’s partners. These updates include new authentication workflows and events, as well as custom PIN capabilities for more granular control over the authentication process.
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?