In his latest blog, Adam discusses the importance of continuous API documentation as your API collection grows (and likely becomes more complex).
In his latest article, Adam explores the role of the SRE as it relates to API strategy/design, and some of the advantages adopting this role brings to both APIs and business.
In his latest blog, Adam discusses best practices for Continuous API Management , including several significant ways that drives change when the API is operating on cloud architecture. API management, whether on the cloud or off, comes down to discovery, documentation, monitoring, alerting, and authentication/security. How well you implement best practices in these areas will make or break your service. In this article, we’ll summarize several considerations for adapting to the cloud.
In his latest blog, Adam discusses how APIs are the building blocks of the distributed systems that run our world, and how they constantly move data from point to point. He then discusses different API technologies to provide solutions to different pain points in API data exchange.
The latest blog from Adam covers the three primary categories of APIs (Single Implementation, Internal Utility, and External Extension) and when best to choose each.
Our Q1 TechTalk had API Academy members Francois, Aran, and myself reminiscing about the 20th anniversary of Layer7 and the 10th anniversary of API Academy – and many of the “things” that have come and gone over the last 20 years – with a dive into protocols – past, present, and emerging. Definitely worth a watch!
Register for our Q1 TechTalk, where we’ll be discussing API protocols – past, present, and future. See you there!
How do you expand API functionality while also ensuring existing mission-critical features continue to operate under stress? API development teams tend to focus on new features, while operations teams focus on stability. In the past, this difference in focus often led to these teams working at cross-purposes and made API development difficult. In recent years, […]
Your company provides a lot of APIs to both external and internal consumers. Your API landscape is every API you’ve built, plus those in the early stages of design and development. Before you can make decisions within this landscape—such as which APIs are working well, which may need to be shelved, and which may need […]