Systems | Development | Analytics | API | Testing

Kernighan & Pike, The Practice of Programming, 1999 Despite constantly changing technologies and the needs of customers, some wisdom seems eternal. Programmers need to test their code. But thorough testing takes time. When we do it well, everything works, and a massive testing effort feels like a waste. However, when we do it badly, our code is often broken, and we wish that we had done better testing. I have some good news for you.

For a software engineer, even the basic use of a debugger can save a lot of pain: adding breakpoints (places in the code the program will stop at and expose the current context) is very easy, and navigating from one breakpoint to another isn't difficult either. And with just that, you can say goodbye to a program's many puts and runs. Just add one or more breakpoints and run your program.

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.

Docker has revolutionized application deployment, offering flexibility and efficiency through its containerization technology. As Docker environments evolve and grow, managing resources like containers, images, volumes, and networks becomes increasingly challenging. Docker Cleanup addresses this challenge by providing a systematic approach to identify and remove unused or unnecessary resources. In this blog, Let us explore the essential commands and techniques for cleaning up Docker resources effectively.

Discover alternative mobile app distribution platforms as Microsoft phases out AppCenter. This post provides insights into the essential features of a good distribution tool and guides you in selecting the best solution for your app release needs.

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.

Node.js 22 has been released, offering a compelling upgrade for developers. It takes over the 'Current' release line, while v21 transitions into maintenance mode until its end-of-life in June. This release delivers advances like a stabilized Watch mode, pattern matching support in the fs module, a default-enabled WebSocket client, and a new--run flag for script execution. It also offers some performance improvements and the usual V8 engine upgrade.

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.