With the global increase in digital adoption, our customers must build better digital experiences for their own customers to stay relevant. There are, however, many underlying components that need to be stitched together and maintained before an organization can start building digital experiences. This process is complex and time consuming, and there are very few organizations that have the capabilities to do so.
It’s no secret: we’re fans of API first companies like Twilio. With more than ten million customers using their platform, it seems we’re not alone. Longtime the darling of developers, Twilio’s approachable platform makes it easy to send voice, video, and SMS messages across nearly any context. Today, we’re diving into how Twilio still offers the best in customer engagement.
Many API developers and companies struggle to find ways to easily set up systems to monetize their APIs. Some are simple but not customizable, some are complex and require massive engineering effort to actually get it all running. To make things easier, Moesif created a feature a few months ago called Billing Meters which gives massive customizability but with a minimal amount of code and engineering effort.
Kong Gateway is built on Nginx/OpenResty because it has a unique master/worker architecture, forks out many worker processes, and can utilize every CPU core efficiently. It is the powerhouse within Kong. But one master / multi workers architecture has an annoying defect. Each worker is an isolated process, so it is hard to share something with each other, and in Kong Gateway, there’s a lot of information to communicate between workers, like rebuilding router/health check/cluster sync, etc.
APIs are a key aspect of our digital world and allow us to engage in digital experiences on our phones and computers every day. Every time you use an app such as Facebook or Instagram, check the weather or send an instant message, you’re using an API. So what are APIs? API stands for Application Programming Interface, which enables communication between two applications.
Sometimes you may want to limit the amount of analytics data coming into Moesif. This could be because you want to exclude specific traffic, such as internal or health check traffic, or you may want to reduce unnecessary data to control cost. Dynamic Sampling, available to customers on our Enterprise plan, was built to do just this. Dynamic Sampling lets you control which API calls are logged to Moesif based on customer or API behavior.
