Uber processes data for millions of trips in over 400 cities in 60 different countries on a daily basis. Needless to say, that’s a lot of data, and finding a way to optimize their JSON payloads was an important goal for the Uber engineering team.
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 a previous post I covered six great ways to engage your API community. It was based on seeing thousands of APIs—some that received developer attention and some that fell flat. Now I have dug into ProgrammableWeb’s directory to find the features that really seem to make a difference. Comparing the top 100 APIs to the rest of the pack, it’s clear that community support is a huge differentiator.
APIs and data delivery go hand in hand, with APIs being the core mechanism for transferring information between dissimilar systems. Web applications have relied on APIs for a variety of tasks and chores, making coding for API integration a core competency and critical element for those building Web applications.
In this article Uri Sarid, CTO of MuleSoft (parent to ProgrammableWeb), discusses the approaches to API-first design. He touches on the value of this approach and how it allows businesses to optimize for a great API instead of having the API simply be a reflection of existing code.
For many APIs, a developer portal is the first interaction a developer will have with the API. Typically, this is where a developer finds documentation, code examples, an app gallery and other details that connect them with the API provider. If you want developers to use your service, you'll aim to make everything within the developer portal as clear as possible. Consider these six steps to bring clarity to your current and future developers.
The adoption of REST as the predominant method to build public APIs has over-shadowed any other API technology or approach in recent years. Although several alternatives (mainly SOAP) are still (very) prevalent in the enterprise, the early adopters of the API movement have taken a definitive stance against them and opted for REST as their approach and JSON as their preferred message format.