The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "Analysis"
When Yahoo! shut off a stock quote service that developers were relying on -- albeit anonymously -- developers erupted with disappointment and anger. But those developers were probably trespassing on the service and Yahoo! had no way to notify them of the shutdown. Maybe a standard can fix that.
Everywhere you look, you'll find old business processes that have been in place for decades. When many of these processes went online, chances are they were reproduced, step-for-step, electronically. No one bothered to think differently about those steps. Jetty is example of one company that did.
Developers were angered when Yahoo Finance deactivated a CSV download feature that was being treated as an API. As a result, it appears as though several applications broke and developers voiced their disappointment. But, as it turns out, they were taking a big risk in the first place.
Despite the fact that the costs associated with hacking and data breaches have arguably never been higher, recent API-related security incidents involving large companies, T-Mobile and Accenture, highlight the fact that basic API security best practices are still often not being adhered to.
Cloud-based apps rely on an increasingly diverse set of underlying services, tied together through APIs - and hackers have taken notice. To resolve attacks and outages affecting APIs it is critical to understand and test the performance of the service delivery of application components.
Developed app markets are increasingly saturated making it harder than ever to stand out. Localizing your app abroad - whether just a translation or a full app overhaul - could be the difference between its global success or failure. So what should you consider if you want to localize right now?
For a profession that stresses the importance of naming things well, we've done ourselves a disservice with microservices. The poor naming has led to misconceptions and misapplication of microservices by those hopping on the bandwagon, many times without deep understanding of its concepts.
Among a slew of product announcements, Google introduced its latest smartphone; the Pixel 2. The new smartphone packs some incredible capabilities, especially when paired with Google's new Pixel Buds. But as industrial designs go, the Pixel 2 is nothing special to look at. But that doesn't matter.
Deciding what metrics matter depends on the overall strategy goals and business model that aligns with your APIs. This is why defining the business model was one of the first steps in your decision series. Now we need to make sure our evaluation framework matches back up to what we set out to do.
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?
Congratulations, your API is now production ready. Next you will need to provide documentation to consumers so they can integrate the data and services you have exposed via API quickly. This part covers API documentation including the role of API specs and a number of available tools.
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.
With business decisions in place for your API strategy, we've moved on to some more technical issues, such as the reference and API architectures, and the choice of API specification formats. Now in this part, let's take a look at the range of API lifecycle tooling available.
The first few decisions around building an API strategy centered on the business components. With those in place, building the API is now possible. The API strategy moves to becoming more of a technical concern for several steps as you resolve API design, security, and API Ops.
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.
When defining your API strategy, a crucial decisions to make is what API business model will be used. A business model is a way to understand all of the system components that come together to allow you to create a project and add value. It helps you answer how you will make money from your API.
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.
This is Part 3 of ProgrammableWeb's series on maximizing the ROI on your API. In this part we explore how to build a team that can build internal support by liaising with various business units. The article also looks at putting together the right team to drive your API strategy.