The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "Analysis", Article Type: "Off Hours"
Today, on the heels of news about concerns regarding the use of certain fitness technologies that could reveal confidential military troop and base locations, comes an entirely different spectrum of issues to consider before allowing for public or partner consumption of your APIs.
Switching from one programming language to another can be a monumental step for any team. This past year, the team at Stream switched its primary programming language from Python to Go. Leaving Python behind was a big step for us, but using Go gives us advantages we couldn't ignore.
Today the conditions are more favorable than ever for organizations to consider implementing event-driven non-polling based data retrieval patterns in their APIs. This series aims to help you to better understand your options when it comes to push/streaming API architectural styles.
The previous parts of this series helped you become familiar with various kinds of push technologies. Sometimes you will want to build your own push API from scratch. Other times that isn't the case and this article helps familiarize you with some of the turnkey push API infrastructure providers.
A good API is the secret to being able to test earlier, which means finding problems earlier in the software process. Perhaps earlier enough to prevent the delays, certainly earlier enough to save time. If you want to test earlier and be more effective, this is the place to start.
The best workflows direct customers through business processes, guiding them along each step they need to take to reach their goals. They also give developers good starting points for testing. But how can API testing workflows help teams figure out where to start, and know when they're done?
This is the final part of our API Testing series. In this article we will talk about what's coming up in the near future that will change how we test and deliver new APIs. Included are looks at the possible effects of newer architectural styles such as GraphQL and gRPC, and new tooling.
Even though Webhooks, PubSubHubbub, and WebSockets are really popular, they aren't the only options at your disposal. This part of the series provides overviews of a number of other push alternatives that you might find helpful for meeting the needs of your particular application.
How to Create a Quick and Dirty Example of The Proposed Standard for In-Band API Service Warnings API University
As a best practice, API providers often go to a lot of trouble to notify developers of upcoming disruptions or changes to their APIs. All of this happens out-of-band like in a ChangeLog or an email. But how about the idea of in-band notifications, especially when developers are impossible to reach?
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?