On Tuesday, social media giant Twitter announced that it is buying Data as a Service (DaaS) provider Gnip for an undisclosed amount. Gnip, which is one of several companies that sell access to the firehose of the content posted on Twitter, was founded in 2008 and today offers data from a number of popular user-generated services in addition to Twitter.
After acquiring InsightsOne earlier this year, Apigee is now ready to show the first fruits of that labor. Apigee today launched an upgrade to the Apigee Insights Big Data analytics platform, that is tightly integrated with the Apigee Edge API management platform.
Today, SmartBear announced the general availability of SoapUI 5.0. SoapUI was specifically designed to tame the growing number of undocumented REST APIs on the market today. In preparation for the launch, ProgrammableWeb caught up with Matti Hjelm, SmartBear’s SoapUI Product Owner, to learn more.
The API maturity cycle within the enterprise is evolving at two or three times the speed of previous software oriented architecture (SOA) cycles, creating an urgent need for tools that ensure new business integrations built with APIs are managed with respect to governance and industry regulatory requirements. To keep up with this pace, SOA Software has today released the Lifecycle API. This new API is part of the company’s Lifecycle Manager product that supports enterprises with flexible approaches to governing IT and business activities and processes.
There are plenty of tools for those that create and manage APIs. But when it comes to those that need to consume those APIs there are not so many. Looking to rectify that situation 3Scale, a provider of API management tools, launched a beta version of a free APItools service specifically designed to meet the needs of organizations that need to consume APIs.
A series of conferences known as the Nordic APIs have started a four-day tour of four countries in Northern Europe. The mission: Bringing API discussions to the capitals of Sweden, Denmark, Finland and Norway. Presentations by sponsors MuleSoft (parent company of ProgrammableWeb), Ping Identity, Twilio, Axway and Layer 7 are joined by local speakers in each country under the overarching theme of “Private, Partner and Public APIs.” The first event, held in Stockholm today, was fully booked, with events in Copenhagen and Helsinki also expected to reach audience capacity. ProgrammableWeb spoke with presenters and participants at the opening event.
3SCALE recently announced the launch of the 3SCALE AWS API Proxy. The new offering allows anyone to setup an API management proxy on Amazon’s AWS infrastructure. To learn more about the new API proxy, ProgrammableWeb caught up with 3SCALE CEO, Steve Willmott.
U.S. Government officials are being encouraged to provide comments and suggestions for a standard API Terms of Service (ToS). The hope is that a standard ToS could be used by any government agency making open data accessible via API. Launching the consultation via the Government API Google Group and on Github, key stakeholders believe the time is right to streamline the process of making API Terms of Service more relevant to developers who want to make use of government open data sources. Developers are now adding their feedback and perspectives to a Github issues repository.
There are major advantages to today’s applications being built atop APIs. If you’re reading ProgrammableWeb, there’s a good chance you know all about integrating with other services. The major disadvantage of modern distributed architecture is pretty obvious—someone else’s service could go down and it’s outside of your control. You might not even know a service is down, which is why many top API providers are now making status pages available. These sites help communicate to developers when anything is amiss with the API.
In some of my more recent posts, I have written about upcoming transformations within the API space, ranging from orchestration layers to how Netflix pursued an optimized API design for the 1,000-plus device types that it supports. In this post, I will provide more context for these decisions and how they may (or, perhaps more likely, will) apply to your API designs–especially when it comes to the benefits of the separation-of-design model.