In order for APIs to deliver on a myriad of benefits and objectives, organizations must design them with scale in mind. However, the need to build high-performing APIs that scale with the business ecosystem is pressuring many development teams to build APIs that may be restricting business growth.
API Education Articles
The following is a list of ProgrammableWeb articles that matched your search term. On an nearly 24/7 basis, ProgrammableWeb publishes new articles ranging from news to opinion to tutorials for both developers and API providers. All of our articles are categorized in such a way that you can find your way to related articles, APIs, SDKs, Libraries, Frameworks, Tutorials and Sample Source Code. If you have an interest in contributing any of the aforementioned content to ProgrammableWeb, be sure to read our guidelines for such contributions.
Our series on getting the most ROI out of your API has looked at the business and technical decisions to make when building your API strategy. We've also made decisions around how to engage with developers and build a developer community. A key aspect to this involves creating a developer portal.
Now that your API has been published and external developers are beginning to consume it, our focus shifts again towards a balance between business and technical issues. In this part of the series we take a look at how a business can leverage the technical API to grow a developer community?
At this point in your API journey, you have made a number of business decisions and a couple of technical ones. Now, several crucial decisions need to be made around security. Securing an API is an often neglected task, yet doing so is at the heart of an effective API strategy.
As you go through the decisions involved in setting up the business side of managing an API, it becomes clear that you will need to treat the API as a product in order for it to succeed. But what does that mean and how do you do that? This part takes you through the things you need to consider.
At this point in an organization's API journey, the groundwork has been laid and it is time to think about one of the first big decisions in creating our APIs: which data and services to open first as APIs. This article looks at how different API business models can affect this decision.
When a business starts its API journey, it has to make a number of key decisions. Not surprisingly, at each decision point, multiple options branch out it can become easy to become confused and cautious quickly. How do you make the decisions to embark on a successful API journey?
On April 20th in San Francisco at MuleSoft's Connect conference, ProgrammableWeb's David Berlind is hosting two separate sessions. One is a panel discussion talking about options to the REST API architectural style and when they're appropriate. The other session is on building developer community.
The API is at the heart of the technology of every connected person’s daily life. Mark O’Neill, research director at Gartner, presented some of the trends in the API industry at a recent APIDays conference. This article delves into them and how they affect the future of the tech industry as a whole.
The Japanese have five essential elements of life, known as the Godai: Earth, Water, Fire, Wind and Void. In this article Rebrandly discusses what it feels are the five Godai elements that an amazing API requires: Design, Scalability, Reliability, Security and Documentation.