The AWS Neptune Java SDK interacts with the API to access cloud services. See folder model at https://github.com/aws/aws-sdk-java/tree/master/aws-java-sdk-neptune/src/main/java/com/amazonaws/services/neptune
Need to make sure your cloud is up and running? If you like pretty charts of that uptime, Nimsoft has got you covered. The company also has a not quite as pretty Nimsoft Cloud Monitor API that allows developers to integrate the tools for monitoring cloud performance into their applications.
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?
At the Google Cloud Next event in London this week Google offered updates to both its Google Cloud Natural Language API and Google Cloud Spanner. The former gained a bevy of new languages and tools, while the latter graduated from beta status to general availability. Here's what you need to know.