Moesif offers self-service analytics for everyday use, as well as features that aid with cost-effective analytics expansion. Customers use it to monitor features to better understand when there are API difficulties, and there are extra features to determine who is using the API, how often they use it, and who is likely to discontinue using it based on how they use it.

In this blog post we’ll help answer the age old question, “What does this service talk to and what does it say?” We’ll see how to inspect inbound and outbound REST API calls to see what calls are being made and what incoming traffic causes a reaction. This can be pretty handy when you’re taking over maintenance of an existing service, or if your code just isn’t behaving the way you expect.

Composable business. APIOps. Hyperautomation. Open policy agent. These are among the themes we’re expecting to hear a lot more of in 2022. Here are 12 key developments we’re beginning to see in the world of digital transformation, APIs and the cloud.

Apigee is committed to continually innovating new capabilities and solutions for our customers, and 2021 saw new product launches, partnerships, and best practices for managing your expanding range of business-critical use cases. Here are some of our favorite stories from 2021.

In this episode of Kongcast, I spoke with Jason Yee, director of advocacy at Gremlin, about the concept of chaos engineering, why even the best engineers can’t control everything, and tools and tactics to help build app resiliency. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.

As project needs evolve and expand, people need tools or software to enhance business operations and improve productivity. Over the past few years, several frameworks have been designed to aid the development of such tools and software, and among them webhooks are prominent ones. Webhooks are essentially tools used to automate business processes and allow organizations to provide interactive capabilities to customers.

Enterprise Integration Platform as a service (EiPaaS) is commonly used to describe a suite of cloud-based tools and services that are designed to support enterprise-grade integration strategy and initiatives. The hallmarks of EiPaaS products are ease-of-use, standardization and pre-built modules such as connection endpoints (usually API-based, to connect to a business application like CRM or ERP), automation flow builder and error handler.

Before exposing your company’s APIs, your highest priority should be to assure the security, governance and reliability of those APIs. To do so, you’ll need to use an API gateway as a single secure entry point for API consumers rather than allowing direct access to APIs. Kong Gateway can help manage the full lifecycle of services and APIs as well as secure and govern the access to those APIs within an API platform.

For the modern enterprise, the focus on customer obsession—an endeavor shown by research to bring better revenue growth and customer retention—requires connectivity across all of an organization’s resources. Back in the day, the Enterprise Service Bus (ESB) was the primary provider of connectivity for a service-oriented architecture (SOA).

This year, we hosted our inaugural Kong Summit Hackathon. This virtual competition engaged our open source community and offered recognition and prizes for hacks in various categories. The community delivered with ingenious plugins, hacks and documentation. This blog post highlights our Kong Gateway plugin winner, Narendra Patel. Narendra is a senior DevOps engineer at Egnyte with close to 10 years of experience as a developer, DevOps engineer, SRE and in RPA (robotics process automation).

Let’s boldly go where no one has gone before. Get ready, Star Trek fans! Jean-Luc Picard will be representing our microservice. Once we have Jean-Luc in our ship (microservice in production), what happens on day 2? We still need to add authorization, load balancing, rate limiting, etc. With an API gateway, like Kong Gateway, you don’t have to know how to do this because a set of program components, called plugins, allow you to implement this without any problem.

Today, we are welcoming another noteworthy advancement of the Kong Gateway – the general availability of version 2.7! Both Kong Gateway and Kong Gateway OSS version 2.7 downloads are available on your favorite distribution channels. This release of the Kong Gateway includes a number of important features that serve as a foundation for addressing three key areas.

If you’ve been online at all this week, chances are that you’ve heard about the Log4Shell zero-day (CVE-2021-44228) in Log4J, a popular Java logging library. The vulnerability enables Remote Code Execution (RCE), which allows attackers to run arbitrary code on the target’s machines. I know the first question that you all have is: “Is Kong affected by Log4Shell?” Let’s start with the good news: No Kong products are affected by this Log4J vulnerability.

In the KuppingerCole API Management and Security Leadership Compass 2021, Lead Analyst and CTO Alexei Balaganksi states, “Our general recommendation for customers remains the same: both API management and API security should not be considered as standalone, isolated components of your IT infrastructures.

RealWorld is a popular open-source project known as the mother of all demo apps. It is an exact clone of Medium.com (called Conduit) and can be built using any front-end and back-end. This article will share the journey to replicating the RealWorld REST API (Conduit) from scratch using Linx, a low-code developer tool. All stacks that integrate with Conduit will integrate with the newly created API. Technologies and tools used to develop RealWorld API: Notes

In this episode of Kongcast, I spoke with Scott Lowe, principal field engineer at Kong, about what a service mesh does and when to use it, among other common mesh-related questions. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.

REST and (the newer) GraphQL APIs are the core technologies behind the vast most of today’s integrations. These APIs allow external developers to tap into the functionality of the major platforms and build in their custom functionality to suit their needs. The fundamental difference is that REST is an architectural design framework based on HTTP, while GraphQL is a query syntax that is not transport-dependent.

This blog was co-created by Ricardo Ferreira (Elastic) and Viktor Gamov (Kong). We love our microservices, but without a proper observability (O11y) strategy, they can quickly become cold, dark places cluttered with broken or unknown features. O11y is one of those technologies deemed created by causation: the only reason it exists is that other technologies pushed for it. There wouldn’t be need for O11y if, for example, our technologies haven’t gotten so complex across the years.

Webhooks vs API, oh well. When there is a talk about what method to use in order to seamlessly sync datasets between applications, platforms and databases (in other words, to perform application integration), APIs are often named as today’s best-practices method for handling this.

As more companies invest in a cloud native infrastructure, they’re choosing to prioritize their applications as microservices—architecting them into distinct servers. Each component is responsible for one (and only one) feature. For example, you might have Server A responsible for handling billing logic, Server B for handling user interaction and Server C for handling third-party user interactions.

At Kong, we run performance testing in CI in every commit or pull request that has a potential performance impact, as well as on each release. Thanks to the performance testing framework and its integration with Github Actions, we can easily get basic metrics like RPS and latency. Also, flame graphs to pinpoint the significant part that draws down performance. With that workflow in place, we figured one of the most significant parts of Kong’s hotpath is Nginx variable accesses.

As part of the Kong Gateway 2.6 release, we shipped a brand new jq plugin for anyone with an enterprise license to use. It’s like we combined the request and response transformer plugins to form a single, more powerful plugin—supercharging the way we work with request and response bodies. If you’re not familiar with jq, it’s a JSON processing language that allows you to manipulate any JSON document and transform it however you need.

Snowpark has generated significant excitement and interest since it was announced. Snowpark is a developer framework that enables data engineers, data scientists, and data developers to code in their language of choice, and execute pipelines, machine learning (ML) workflows, and data applications faster and more securely. While many parts of Snowpark are in preview stages, External Functions entered General Availability earlier this year.

One of the best features in ThoughtSpot Everywhere is the Developer Playground. The Playground lets frontend Developers visually configure elements and generate JavaScript code to add into your web app. It is an amazing tool for testing and iterating configuration options before adding final elements such as Search, Liveboards, and visualizations into your web app. But what about a backend Developer who might be building solutions that utilize the Platform’s APIs?

Without users, products mean nothing. So why is it that so many organizations analyze API and user behavior metrics as an afterthought? My theory would be that they just don’t have the right tools in place to actually collect, analyze, and use these usage metrics. With so many products aiming to improve their user experience and customer satisfaction, tools like Moesif are exactly what is needed.

When looking at API analytics and monitoring platforms, many seem to be so similar that it’s hard to figure out the differences between them. We often hear this confusion from users and prospects. In a world with so many tools available, how do we figure out which ones are necessary and which are redundant? One of the most common questions we are asked revolves around how Moesif compares to Datadog and how they could work together.

The Neosec platform integrates with Kong Gateway Enterprise to provide automated and continuous API discovery, API risk posture alerting and API protection through behavioral analytics and response automation. And it does all that while being out of band, using the logs shipped from Kong to Neosec.

Although the RESTful Application Programming Interface (API) was first established in the year 2000, there are currently no set guidelines or standards for API development. Developers have experimented with many methods to improve REST API solutions throughout the years. Some of them were successful, while others were unsuccessful. APIs that are poorly developed is difficult to maintain over time and are prone to failure.

For those who aren’t familiar with Insomnia, it’s Kong’s API testing, design and debugging platform. Insomnia’s product vision is to optimize API development by simplifying and automating a developer’s workflows. APIOps plays a key role in this vision, optimizing API development by simplifying and automating developers’ workflows.

Over the past two decades REST APIs have emerged as a lightweight and flexible standard for enterprise data and backends get exposed to external, partner, and internal applications. Google Cloud’s Apigee is a leader in API Management, allowing users to manage REST APIs — define rate limits, enforce authentication and authorization, block clients that attempt to misuse an API, and ensure APIs work seamlessly as they are updated.

Joining us is Phil Nash, leading developer evangelist at Twilio, a Google Developer Expert and a member of the Live Coders team on Twitch. He’s a regular conference speaker where he sometimes writes code on stage and hopes everything just works.