Exceptional customer experience is vital to building a successful business. A recent report from Forrester Research shows customer-obsessed companies reporting 2.5x higher revenue growth and 2.2x better customer retention. Application Programming Interfaces (APIs) play a key role in providing customers with stellar digital experiences.

Open banking is a natural evolution in the API economy. By laying the foundation for web platform and mobile developers to build third-party products and services using any number of public (open) APIs, banks, financial services and insurance companies are ushering in next-generation customer experiences that are more frictionless and personalized.

This is Part 1 of a three-part blog series that will dive into industry insights from technology leaders who are facing the next wave of digital innovation head-on. Today, we meet again at the cusp of the next frontier. This time, it’s Web3, the metaverse and boundless connectivity. Businesses everywhere are bracing for what’s next while preparing for the onslaught of new-wave digital experiences.

Once you decide to monetize your app or APIs, the journey begins to find a simple and robust solution for billing. At Moesif, we know that a billing solution is actually really tough to implement. Getting your product from “0-to-monetization” is not always a straightforward path, even if it should be. Our no-code approach to billing is a simple and elegant way to very rapidly gain the capability to bill customers for usage.

Speedscale is delighted to join the Google Cloud Partner Advantage program as a technology partner giving GCP customers the ability to stress test their GKE clusters under production-like workload conditions.

This is part of a 3-part series on APIs, sustainability, and climate change. Check out part 1 on managing a greener API lifecycle, and part 2 on ways to embed and innovate on top of third-party APIs to make greener products. In this final part, we will look at the environmental impact of common architecture trends and recommend steps to take to minimize the impact of each.

While the year 2021 was a huge success, we've re-energized ourselves for 2022. By launching new cloud platforms, we began our path to radically simplify the production of digital experiences for our clients. This allows us to offer products and solutions as software as a service (SaaS), private cloud, or on-premises, with the ability to seamlessly move between the three alternatives in the future.

Go, often referred to as Golang, is a popular programming language built by Google. Its design and structure help you write efficient, reliable, and high-performing programs. Often used for web servers and rest APIs, Go offers the same performance as other low-level languages like C++ while also making sure the language itself is easy to understand with a good development experience.

A good business model is one that can easily generate revenue. Often, when developers build something it could easily be packaged and used by another organization. This is extremely true when it comes to APIs. If an API is solving a well-known problem, there is likely a market for it. Being able to expose an API for public consumption can be done in many ways, a popular option being using an API gateway. The real hurdle comes when you decide to start billing for usage.

Recently, I was fortunate to have an insightful conversation with Matt Klein, Lyft software engineer and creator of Envoy, the popular open-source edge and service proxy for cloud-native applications. Envoy was the third project to graduate from the Cloud Native Computing Foundation (CNCF), following Kubernetes and Prometheus. Before Lyft, Matt held positions at Microsoft, Amazon and Twitter, and served on the oversight committee and board of the CNCF.

Customer identity and access management (CIAM) has become indispensable for organizations. According to an article by the Business Research Company, the CIAM market is expected to reach $45.56 billion in 2025, at a compound annual growth rate of 18.6%. The research firm adds that the increasing use of Internet of Things (IoT) devices — such as smartphones, smartwatches, smart homes and medical sensors — will be the primary driving factor for this growth.

AWS Lambda has been around for a few years now, and it remains the most popular way to experiment with serverless technology. If you're not familiar with serverless, it's a model of development in which managing, provisioning, and scaling servers is abstracted away from application development. Servers do exist in a serverless world, but they are completely managed by the cloud provider, allowing developers to focus on packaging their code for deployment.

In this Kongcast episode, Josh Long, Spring Developer Advocate at VMware, dives into how Spring changed the way developers build Java applications and introduces you to Spring Native. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.

Interdependence and collaboration between businesses and commercial sectors have changed in recent years with the use of Application Programming Interfaces (APIs). APIs have been around long enough for companies to know that they can use open web technologies to extend their services via in-app integrations. APIs allow two programs to communicate with one another and exchange data in a smooth manner. Once an API has been created, it is vital to test the interface to ensure that it is functional.

Elasticsearch is an open-source search engine and analytics store used by a variety of applications from search in e-commerce stores, to internal log management tools using the ELK stack (short for “Elasticsearch, Logstash, Kibana”). As a distributed database, your data is partitioned into “shards” which are then allocated to one or more servers.

TBC Bank is a technology-driven company in Georgia. We are happy to announce that we have chosen Kong to improve our API ecosystem and leverage its technological resources, expertise and international footprint to further simplify the daily lives of our users. TBC wanted to partner with a company that, in addition to providing the technology platform required to publish APIs in our bank, would also offer a strategy for developing and implementing API management principles.

This is the second part of our three-part blog series on APIs, sustainability and climate change. Missed the first part? Check it out here. In this blog, we examine ways to consume and embed APIs to make our own processes greener and show how APIs are the building blocks of a new wave of green innovation. The API economy – and therefore the ways we can use APIs to cut carbon emissions and make technology more sustainable – is not just about building APIs but consuming them too.

It’s always great to build something that makes money. The most successful businesses often find the easiest and most efficient ways to make money, while keeping costs and support to a minimum. After all, the best businesses and products are simply the ones that know how to build revenue. Many companies now look to monetizing their APIs as part of their overall monetization strategy. API monetization isn’t always easy though.

Building great apps and APIs is not an easy task. Even harder, is trying to monetize and create a sustainable business with them. As part of our mission to help companies create better products, we decided to put a bunch of effort towards helping businesses more easily monetize. Our no-code approach to billing is a simple and elegant way to very rapidly gain the capability to bill customers for usage. Easy monetization is the premise for our latest feature for generating revenue from your APIs.

While APIs are often called as the new standard for integrating business applications, the topic of webhooks integration seems to be largely underrepresented in the how-to guides and reference literature. This is unfortunate, because actually, webhooks represent a powerful mechanism that allows to build event driven integrations with quite a high level of customization and functionality.

The proliferation of microservices has led to many new innovative approaches in the software world. However, building robust, quality APIs that consistently deliver the business outcomes you desire can be a complex task. It’s no wonder a recent survey of organizations adopting microservices found that nearly 30% of the respondents listed “API quality” as one of their biggest challenges. API-based applications don’t just come in one flavor.

This article helps you learn more about the Bitrise API and how to make the most out of it — with real examples from members of the Bitrise community.

With over a billion more mobile devices projected to become connected over the next year, it’s never been more important to ensure SLA performance and functional reliability for business-critical APIs. While QA, development, and SRE teams have traditionally relied on API load testing and uptime or ping monitors to mitigate performance risk, too many companies have felt the pain of APIs, mobile apps and web platforms failing under stress or unexpected traffic patterns.

We’ve been hard at work over the past year with new features every month, and we’re super excited to tell you about the new capabilities. Our product roadmap focus has been relentless. Helping your teams get: All of this while making Zephyr Enterprise more scalable and secure for your teams. We know how important these themes are, and we’re committed to meeting Enterprise teams where they’re at, and getting them to where they’re going.

Savannah Whitman When your platform runs on APIs, all of those APIs need to run perfectly. Quickly resolving issues in your API isn’t just helpful, it’s mandatory. Latency and error monitoring are only the beginning: a healthy server isn’t the same thing as a healthy product. Resolving error cases and API abuse is easiest with full visibility into your API, which is where API analytics come in.

The quest for resilience and agility has driven us into the modern age of microservices. Bringing services to market on a microservice architecture demands utilization of sprawling technology offerings and tooling. While daunting at first glance, we can break down the process into 3 major categories: In this hands on series, we will use.

When you need two or more applications and services to exchange data between them on a regular basis, REST integration (or REST API integration) is one method that slowly but steadily gains status of the new and preferred standard. But as with any other project where you need to connect apps and web services via API, integrating REST requires good preparation and a solid methodology to avoid project delays, development overhead and too many errors. So, how do you do REST integration the right way?

ContainIQ runs all infrastructure on Google Cloud (GKE), and was able to get Speedscale installed within a few minutes. After installing the Speedscale operator, ContainIQ began capturing traffic from the primary gateway where service calls come into a cluster.

It’s prudent business practice to only focus on your core features when getting to Minimum Viable Product (MVP). Microservices architectures allow you to outsource non-differentiated pieces of your solution to third-party providers; Use someone else for user management, billing and account management. At first blush, it might seem attractive to develop your own API analytics solution, perhaps by building on top of a web analytics tool like Amplitude, MixPanel or Segment.

New technologies always require some planning, changes, and experimentation before they merge into an enterprise stack. GraphQL adoption has been no exception to this. Companies like Airbnb, Netflix, Shopify, and other industry giants have all taken the leap to use this promising technology. In this blog, I will outline a few key considerations for creating your new service, deploying it, and monitoring the service.

The Google BigQuery Write API offers high-performance batching and streaming in one unified API. The previous post in this series introduced the BigQuery Write API. In this post, we'll show how to stream JSON data to BigQuery by using the Java client library.

The API management space is changing – fast. In the past couple of years alone, we’ve seen huge changes in the deployment patterns that our customers are adopting. In the past, when the use cases were fairly simple, organizations would deploy an API gateway as a SaaS monolith in the cloud, sitting at the edge of the network. They did this because it was the best option available at the time, and the first wave of API management vendors like Apigee had a solution that could support it.

In this article, we will take a high-level look at the differences between an API proxy and an API gateway. When a developer publishes a public API, it’s necessary for that API to have security policies and a way to hide backend logic from API consumers. Decoupling your API from your backend services allows you to shield your apps from backend code changes, and allows users to call your API without worrying about availability.

I’ve just got off a call with one of the largest banks in Sweden, and my brain is racing with ideas. I need to get this down on paper. I want to drop everything I’m doing and spend the next week in that mental headspace where all you do is explore and live and breathe a topic, with occasional breaks for sleep, after which you race out of bed so you can go back to where you left off. You know what I mean. What’s got me so fired up? Climate change.

If you found this article, chances are you already know why you need a solid eCommerce and ERP integration. After all, ERP is kinda of the backbone of any online shop; a master system, if you like, that allows you to effectively handle sales orders and order fulfillments, manage your supply chain and B2B partners, and keep track of the inventory, especially if you sell on multiple channels.

It’s not uncommon for organizations to have to deploy solutions across (or among) multiple security domains. Here, we use the term “security domain” to refer to a segregated network environment, like a restricted internal network or a DMZ. This post will explore some design considerations when deploying Kong Mesh (and Kuma, the CNCF-hosted open source project upon which Kong Mesh is built) in environments with multiple security domains.

In this blog post we are going to cover writing a bare-bones API in ASP.NET that can read, write, and delete data from a test database.

Today, we’re excited to announce the release of Kong Gateway 2.8, which further simplifies API management and improves security for all services across any infrastructure. This announcement demonstrates Kong’s continued commitment to our customers and community by providing a next-generation service connectivity platform to intelligently broker information across modern architectures.

WSO2 Identity Server is the most popular open-source CIAM system on the market, and it is widely used by educational institutions and government agencies as an on-premise CIAM solution. Single sign-on/sign-out (SSO), identity federation, strong authentication, identity administration, account management, identity provisioning, fine-grained access control, API security, monitoring, reporting, and auditing are all possible with WSO2 Identity Server's seamless integration capabilities.