In our last blog post in this series, we discussed our journey designing a metrics pipeline for Kong Cloud to ensure the reliability of our SaaS offering. We discussed how we re-architected our production data pipeline using OpenResty to send metrics to Prometheus and saw huge performance gains. We are now able to monitor high traffic volumes in our system using much less compute power, lowering our costs.
During the Kong Summit in September Dennis Kelly, Senior DevOps engineer, explained how Kong became a core service—and an integral part of the architecture—across brands at Zillow Group. Starting out with a single use case for Kong Community Edition, Zillow advanced to proxying production workloads at scale with Enterprise Edition, automating deployments with Terraform. Kong’s power and flexibility fueled its explosive adoption at Zillow.
Kong’s stateless architecture and lightweight footprint allow it to be deployed in a variety of environments, with few adjustments required for deployment strategies. At Kong Summit, the Kong Cloud team described their experience with deploying a provider-agnostic, globally-available, high performance Kong installation.
Today, we’re thrilled to announce the general availability of Kong 1.0 – a scalable, fast, open source Microservice API Gateway built to manage, secure and connect hybrid and cloud-native architectures. Kong runs in front of any service and is extended through plugins including authentication, traffic control, observability and more.
Today at KubeCon, we announced the launch of Kong Cloud – a fully managed version of Kong Enterprise designed to accelerate large organizations’ digital transformation initiatives. With Kong Cloud, customers can instantly start building cloud native services and connect all their services across different environments, vendors and platforms.
For the last few years, microservices have been gaining popularity as the software architecture pattern of the day. But even as enterprises grapple with how they can undergo “digital transformation,” some startups are looking back to their monolithic roots. Software Engineer Alexandra Noonan topped Hacker News in July with a blog post about Segment’s journey to microservices and back again.
Good API design separates APIs that merely expose assets from those that help developers get things done. As I’ve written before, and as we’ll explore in this article, good design includes the style in which web API URLs are constructed.
The Soviet era left Mongolia with a legacy of manual banking processes that requires huge quantities of paperwork. This means that customers need to visit branches frequently for simple things like changing a PIN number or requesting a credit card. Since we count 2.8 million of Mongolia’s 3.3 million citizens as our customers, this could mean long lines at the bank, with an average wait time of 25 minutes for each visit. We wanted to change that.
As I work with customers around the world and across verticals, I’m struck by a common pattern: many savvy business people and technologists grasp the value of the new application programming interfaces (APIs) they’re creating for external ecosystem use cases, such as providing partners access to data or functionality, but they often see both the APIs they already have and those they build for internal use in a different light — not as software products that let developers
API (application programming interface) testing is a type of software testing that performs verification directly at the API level. It is a part of integration testing that determines whether the APIs meet the testers’ expectations of functionality, reliability, performance, and security. Unlike UI testing, API testing is performed at the message layer without GUI.
