Systems | Development | Analytics | API | Testing

When was the last time you made a major business decision and were completely certain the data behind it was accurate, complete, and trusted? For most organizations, that certainty is less common than it should be. Qlik and Amazon Quick together solve one of the biggest obstacles to AI adoption: knowing whether you can trust the output.

Clinical documentation has become one of the biggest sources of administrative burden in healthcare. Physicians spend hours every week creating notes, updating EHRs, and completing after hours charting. As a result, healthcare organizations are increasingly investing in ambient clinical documentation solutions that can capture conversations, generate notes, and reduce manual documentation work.

Recently someone on our team opened a traffic snapshot and found an HTTP request that was captured with our eBPF capture agent, nettap. Our protocol dissector parsed most of the response correctly, but that correctness ended once the response headers were processed. What they ended up with was a recording of an HTTP request/response where the response body was just an incorrect collection of garbage binary data when it should have been JSON text.

Playwright is a browser automation framework that also ships a built-in HTTP client for API testing. That HTTP client, called APIRequestContext, lets you send requests and assert on responses directly inside a Playwright test – no browser, no separate tool. If your team already uses Playwright for end-to-end browser tests, the API layer requires no separate testing framework. It runs inside the same suite, the same CI job, the same configuration.

When you want to know the last time some user was seen or some resource was accessed/viewed, then usually you reach to a timestamp column and update this to the current time whenever it’s seen or accessed. You may have written this kind of SQL statement (or the equivalent) in your ORM yourself a few times: It looks innocent, but even on reasonably small tables, this can cause slow UPDATE statements regularly.

Until now, sending push notifications to a React Native app with Ably meant registering devices manually through the push admin API, usually from a server. The new plugin moves activation where it belongs: onto the device. We've added first class support for React Native apps receiving push notifications through the Ably PubSub JavaScript SDK.

When the Open Semantic Interchange (OSI) initiative launched last year, it set out to solve a problem every data leader recognizes: the same business metric gets defined a dozen different ways across a company's BI tools, warehouses, and now, AI agents. "Monthly active users" in the CRM rarely matches "monthly active users" in the warehouse, and every new AI copilot added to the stack makes the gap more visible, not less. That initiative has just taken its most consequential step yet.