December 16, 2019
Related Articles (749)
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?
You have a hectic business trip to Seattle coming up and its time to choose hotels. Sure, there's cost, availability, checkout times ad whether it has a pool or gym to consider. But there's another important factor: proximity. The Travel Time API demo uses Seattle. See graphic below. You have 4 meetings scheduled over a couple of days: At Amazon's headquarters, a drop in at Starbucks for a chat with a friend, meet at the headquarters of Walkscore, and then lastly at Zillow.