The Latest News On The API Economy
Searching: No Search Term , Filtered By API: "Netflix"
The need for developer autonomy and process ownership in the Netflix API environment is being addressed by the media streaming service as they assess the relationships between their APIs, microservices, and data consumers. Two Netflix engineering managers discuss several possible solutions.
In 2008 when Netflix announced plans to move to the cloud, most observers were dubious. Now Netflix has become one of the first major companies to exist completely in the public cloud and their architectural shift to cloud based microservices led to many successes in performance and scalability.
The popular microservices architecture for applications distributes small tasks among a suite of independently-deployable services that work in conjunction to create a larger application. This style relies on service discovery on dynamic systems, as discussed in this microservices overview.
Google releases new Gmail API to give finer grained control and greater speed, potentially exploding the number of use cases. More on the implications of Netflix closing its API. Plus: check in to your hotel room with your phone, and Android offers a new camera API.
The Wireless Registry has announced the world’s first free and open proximal API. PrivateFly.com offers industry first automated and instant “buy now” private jet prices with the help of an API. Plus, why it matters that Netflix closed its API.
Later this year, developers will lose access to a popular API. Yesterday, streaming video giant Netflix announced that it will be shuttering its public API on November 14, 2014. A small set of developers including Flixster, Fanhattan and Instant Watcher will continue to have access to the Netflix API.
Netflix's Public API update drops access to expiration dates for titles. What you can expect from Google I/O 2013. Plus: Yookos unveils an API for African developers and techpreneurs and 10 New APIs.
Netflix provides cloud cleaning supplies. Lokad announces big data platform. Plus: 82 entries in the Foursquare Hackathon, Stripe clone lands $13 million, and 11 new APIs.
Hystrix: it's the genus name for "Old World" porcupines, and it's also the latest release from Netflix. But you won't see it in their catalog of movie and TV titles, and you can't add it to your queue, because it's not content--it's how Netflix makes sure its content is highly available. Now, Netflix has made Hystrix open source, for anyone using Amazon Web Services (AWS) to implement in their own cloud applications. Read on for details on this "resilience engineering" code library.
Netflix adds Hystrix to its open source AWS Management toolkit. German Newspaper ZEIT releases API. Plus: SaaS and APIs have disrupted the Enterprise Applications landscape, Gartner on Best Buy's digital edge in retail and 23 new APIs.
Hollywood studios haven't released their good fall movies yet. TV shows like Game of Thrones, Mad Men and the like are months away from their next seasons. You need something to watch, preferably right now. Don't worry, the ProgrammableWeb community is here to help you out. Movie mashups are always a popular submission to our directory and last year we took a look at a few of them. Today we'll look at some recent movie mashups that should help all but the most picky viewers find something worth checking out.
On Saturday, September 15th, some major changes will hit the Netflix Public API. Possibly the most significant and likely to impact developers is the removal of user rental history data. The Netflix catalog index files are also being replaced by new versions--and being split into separate streaming and DVD data sets. Read on for more details on these updates.
Facebook only announces breaking changes to the Facebook API once per month, but this one is a doozy. Netflix explains its approach to the Netflix API and how it's blurring the line between client and server. Plus: Washington Post tweets API-first, AT&T shares Watson API and "Twitter is a Corporate API."
Here at ProgrammableWeb, we're huge advocates of API mash-ups and the hackathons which often encourage their development. Earlier this month at Hack the Midwest, the "Best in Show" award went to Qup (pronounced "kyoo-up"), a web application which combines Netflix, Rotten Tomatoes, and e-mail into a handy notification service for movie buffs.
With respect to Web APIs, the industry has clearly and emphatically landed on REST as the standard way to implement these services. And for good reason... REST, which is generally implemented as a one-size-fits-all solution, is an excellent choice for a most companies who wish to expose their content to third parties, mobile app developers, partners, internal teams, etc. There are many tomes about what REST is and how best to implement it, so I won’t go into detail here. But if I were to sum up the value proposition to these companies of the traditional REST solution, I would describe it as: