September 21, 2017
View all 1 Followers
View all 327 Related Articles
Related Articles (327)
Today the conditions are more favorable than ever for organizations to consider implementing event-driven non-polling based data retrieval patterns in their APIs. This series aims to help you to better understand your options when it comes to push/streaming API architectural styles.
LaunchPad Recruits has an extremely simple and clear business plan, and therefore a potentially powerful one. It aims to help companies sift through job applicants faster by supplying video interviews of those applying. Employers can watch the video of them responding to questions, and look at a resume before deciding on a face to face meeting. Have you ever been hiring, only to start an interview based on a prospect's resume and find instantly that the person is not a good match? You can end up wading through an interview, looking in vain for ways to end it early. (See graphic.) The LaunchPad Recruits REST API aims to avoid this by having candidates answer the employer's questions on video before any face to face meeting takes place.
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?