We collect the latest Development, Anaytics, API & Testing news from around the globe and deliver it direct to your inbox. One email per week, no spam.
The service mesh architecture pattern has become a de facto standard for microservices-based projects. In fact, from the mesh standpoint, not just microservices but all components of an application should be under its control, including databases, event processing services, etc.
Looking for an automated test solution that offers unparalleled accuracy? Meet Keploy, your AI-driven API test engineer. Here's a description for "Introducing Keploy | Your Automated API Test Engineer: AI-Driven Edge Cases & No Hallucinations ".
The resurgence of Artificial Intelligence (AI) in recent years owes much to a pivotal moment: the publication of a groundbreaking paper by Google. This event underscores the significant role of Open Source in advancing AI technologies. In this presentation, we delve into how Open Source is not just influencing but also shaping the landscape of Generative AI (GenAI). However, our focus extends beyond the traditional dichotomy of Open Source versus proprietary technologies. Instead, we explore the complementary nature of both realms in fostering the development of the AI ecosystem.
Software testing can feel like you're walking a tightrope—striving to uphold impeccable quality standards while the clock ticks towards your next release. It’s a daunting challenge to make sure every test is planned and executed with speed, all while hoping there are no blind spots in your process. Enter test management. It’s a great way to ensure your tests remain organized, efficient, and consistent. And of course, so you can report on this hard work to leadership.
Things can get tricky when managing pre-paid, pay-as-you-go billing for monetized APIs. Three mechanisms must be in place for this type of billing to work: first, you need to be able to add credits to an account. Second, you need to be able to burn down those credits. Third, you need to be able to block users from accessing the API once they have run out of credits.
API-database coupling vs. traditional multi-layered architectures: what’s the difference and why does it matter? The main difference between direct API-database coupling and multi-layered architectures is that the former allows the API to interact directly with the database, minimizing latency and complexity, while the latter uses multiple layers to separate concerns.
You can use the new comprehensive search bar in Kong Konnect to quickly retrieve the information you need across Konnect entities so you can focus on taking action. Operating through a platform search API, the new search bar’s query syntax offers advanced and precise search capabilities and is designed to cater to a wide range of search requirements, enabling you to find the information you need across different areas of the product with ease and speed.
Now that we have set up our API, integrated it with Kong, and connected Stripe with Moesif, we have the infrastructure to begin billing for API usage. Now, we will move into configuring Moesif with the pricing, metering, and access control/governance pieces of the API monetization journey. Let’s kick things off by setting up the prices we want to charge for API usage in Moesif.