The summer is almost over, so we are taking you back to school with a new edition of API headlines. Here is this month’s API News Roundup – August 2019.
Report: iOS 13 to limit VoIP API for apps like Facebook and WhatsApp, eliminate background activity
A new report today from The Information details a change coming with iOS 13 that will force WhatsApp and others to redesign their messaging apps. The small but notable change has to do with how third-party apps use iOS to make internet voice calls with the PushKit VoIP API and also run in the background which will be restricted come this fall.
Twilio launches SendGrid Ads and new cross-channel messaging API
At its annual Signal developer conference, Twilio announced a couple of new features for developers on its core messaging platform and users of its recently acquired SendGrid email service. The new Twilio tools now allow developers to create multi-channel messaging tools and to get real-time streams of conversations in order to run them through transcription services, a translation tool or other machine learning models.
LinkedIn’s new Audience Engagement API helps marketers discover new audiences
LinkedIn has announced Audience Engagement, a new category of the LinkedIn Partner Program. As part of this program, select partners will have access to LinkedIn Audience Engagement API that will allow marketers with new insights to discover new audiences, serve engaging content and give insights into how competitors are engaging customers. Amobee, Annalect, Hootsuite, Ogilvy, and Sprinklr are the five launch partners for LinkedIn Audience Engagement API.
The importance of API Design
The design and construction of a building is a good analogy to exemplify the importance of API Design. A functional building that meets the residents’ and visitors’ needs with excellence usually starts with a good architectural design, then a good plan, engineering calculations and finally a constructor to do the job.
API workflow design patterns for microservices scenarios
Workflow is fundamental to any multicomponent application. Information moves from the source through a set of processes, and a response of some sort returns as the last step. There are a limited number of ways to steer workflow, and the first step in designing a microservice application is to decide which of those workflow options is best. From there, you can pick from a number of API workflow design patterns.
Mastering the API lifecycle – Part 4 | Sharing APIs with a Catalog
How to Photograph a Black Hole – Observing Microservices with OpenTelemetry
Microservices architecture is a software development architectural style, whereby a complex business problem is solved by a suite of small services. These microservices are loosely coupled and can be developed, deployed, and maintained independently. Each of these services is responsible for a discrete task and can communicate with other services through simple APIs. A single microservice is conceptually simple, but a system of interoperating microservices quickly becomes complex.
Read last month’s API News Roundup.