Multiple teams at Kong have been improving accessibility (also referred to as a11y) across our products. Over the past few months, our Dev Portal team has been working on accessibility improvements prompted by the needs of our customers. For example, financial services and government institutions are required by law to ensure their software meets certain accessibility standards.
We live in an API-driven economy, where Application Programming Interfaces (APIs) are increasingly being used to open new revenue channels, accelerate time to market and democratize data. Enterprises are constantly striving to build faster, more reliable and easier to use APIs. They understand that every time an API is down, unresponsive or slow enterprises run the risk of losing customers, damaging company reputation and losing revenue. At the same time, API security breaches are at an all-time high.
Metered Billing has finally arrived in Moesif and we are super excited to be rolling out this latest feature. We have worked hard to deliver a smooth and simple way to monetize your APIs by allowing usage that is tracked in Moesif to be metered and billed by your favorite billing providers. Moesif can calculate and send usage data to a billing provider so your customers can be billed accurately, based on their usage.
Kubernetes has experienced rapid growth over the years, with a recent post from the Cloud Native Computing Foundation reporting a userbase increase of about 67% in just the past year. Kubernetes is a container orchestration platform that automates how containers are deployed, how they communicate, and how traffic is routed between them; it also scales configurations for both the containerized workloads and the underlying infrastructure that comprises the cluster.
Kong Mesh (and Kuma, the open source project upon which Kong Mesh is built) supports multiple zones and meshes. What is the difference between a zone and a mesh, though? And when should one use a zone versus a mesh or vice versa? By the time you’re done reading this blog post, you’ll have a better understanding of the role of zones and meshes and where each of them fit into a Kong Mesh deployment.