It's 2024, and the HyperText Transfer Protocol (HTTP) is 35 years old. The fact that the vast majority of web traffic still relies on this simple, stateless form of communication is a marvel in itself. A first set of content retrieval optimizations were added to the protocol when v1.0 was published in 1996. These include the infamous caching instructions (aka headers) that the client and server use to negotiate whether content needs refreshing.

Ably CEO, Matthew O'Riordan, recently joined sports and media veteran, Carlo De Marchis, on his podcast ("A Guy with a Scarf") to discuss the dynamic world of realtime fan engagement in sports and entertainment. In the interview, Matt and Carlo cover the evolution of realtime applications and how the changing expectations of fans, particularly younger generations, are shaping the future of fan engagement. Watch the full interview, including Matt’s predictions for the future of this space.

In the fast-paced world of government software development, efficiency and effectiveness are paramount. One way government organizations enhance agility, foster innovation, and optimize resources in the public sector is through citizen development—the practice of allowing non-technical employees to create their own software applications using low-code or no-code platforms.

Interoperability is one of the main reasons to reverse engineer APIs. Unlike a few decades ago, when software could exist in isolation, nowadays, a program runs on a complicated operating system and involves communication with several libraries created by different people. Reverse engineering APIs for interoperability involves API integration and learning new ways in which programs can exchange and use information.

Your Java code was humming along smoothly until... BAM! An exception. No problem, you caught it. But wait, there's another. And another. Suddenly, you're juggling exceptions like you’re in the circus. Don't worry, Java's got your back. Java offers three ways to catch multiple exceptions: using multiple catch blocks for different exception types, the multi-catch feature to handle multiple exceptions in a single block, and a catch-all block for general exception handling.

Since it was created by Facebook in 2012 and made publicly available in 2015, GarphQL has changed everything about how we fetch data from servers for our front-end apps. Most front-end clients typically use REST APIs to retrieve data from the server, this includes mobile apps for platforms like Android, iOS, and Flutter, as well as JavaScript frameworks like React, Angular, Vue, and Next. A huge advantage of GraphQL is that it enables front-end clients to request only the API they require.

Regarding charging for API usage, we usually gravitate towards charging per API call. While this can work for many use cases, it’s not optimal for everyone. This is where choosing the right metric to bill upon and finding a platform that supports it is crucial. In this blog, we will talk about choosing the right metric to bill upon and how to implement it in Moesif. Let’s begin by digging into what a billing metric is and how to decide which one is best to use with your AI APIs and services.