Systems | Development | Analytics | API | Testing

API

KuppingerCole API Management and Security Leadership Compass Names WSO2 an Overall Leader

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.

Building the RealWorld API in Low-code

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

GraphQL vs REST - a low-code API showdown

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.

Creating a User Funnel in Moesif

User funnels allow businesses to analyze how individual users are using and converting within their product. Funnel metrics can show how many users are converting through each stage of the funnel and the average time it takes to do so. In this tutorial, Matt covers how to set up a conversion funnel analysis in Moesif using the User Funnels screen. Steps covered include: Navigating to the User Funnel screen Creating “steps” for each step in the funnel How to read and interpret the output

Building Smart O11y for Kuma With Elastic Observability

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.

Using Elastic ML to Observe Your Kuma API Observability Metrics

Observability is catching on these days as the de-facto way to provide visibility into essential aspects of systems. It would be unwise for you not to leverage it with Kuma service mesh — the place that allows your services to communicate with the rest of the world. However, many observability solutions restrict themselves to the works: simple metric collection that provides them with dashboards. Expecting users to simply sit on their chairs and look at those metrics all day long is an invitation to failure, as we know that one can only do so much when they get tired and bored.

Webhooks vs API: Which is Better To Sync Data Between Apps

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.

Building With Insomnia as a REST API Client

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.