Today we’re launching new names for some of our most popular API products. This is part of refreshing our outlook on the API space and our subsequent API lifecycle tools. We loved our old names, and know many felt the same. And yet, here we are to explain why we decided the progression was necessary.
Consistency is one of the most critical elements of accelerating API development as organizations try to meet increased demand, quality expectations, and regulatory requirements. Without a consistent API design to developers, there is no guarantee that the final result will match the intended purpose or the application depending on the API can function properly.
In 2018, Kong was first positioned onto the Gartner Magic Quadrant for Full Lifecycle API Management Market as a Visionary. This in itself was a very impressive feat given that Kong was started as an open source project just three years before that. I believe Kong’s progress on the Magic Quadrant in this short span of time speaks to how we have aligned Kong’s solutions to our customers’ most challenging problems.
We’re excited to share that Gartner has recognized Google (Apigee) as a Leader in the 2020 Magic Quadrant for Full Life Cycle API Management, marking the fifth time in a row we’ve earned this recognition. In this year’s report, Google (Apigee) is placed highest among all the vendors for the ability to execute.
You have an API program that developers are adopting; Customers have signed up, but some haven’t integrated yet; Of those that have integrated, a few got stuck early on and went silent; Ideally, you’d like to help both sets of customers move through the developer funnel. Moesif can act a catalyst for your developers, proactively informing them of integration issues before frustration sets in and they give up. Ensure they have a good experience – unblock your customers ASAP.
Hiring a New York or Menlo Park white-shoe law firm to write your app’s Terms of Service (ToS) might bring peace of mind, but how do you ensure that your expensive rules are actually adhered to. Just like the pervasive abuse of customer review guidelines in B2C companies, B2B companies also suffer from multiple/unverified review problems. Similarly, by their design, APIs are also vulnerable to misuse by bad actors, but this time through brute force attacks.
As with any product lifecycle, a key responsibility for API architects and API product owners is deciding when to sunset or retire a feature or offering. The API lifecycle is no different, but requires careful planning to carry out the deprecation to minimize customer impact. Unlike a packaged solution or module which is more of a black box, APIs enable your customers to build custom functionality which may have required months of integration work and testing.
