When it comes to closing the technology delivery gap, most organizations are seeing in the IT space, API-led connectivity as the missing link. APIs are a powerful way to integrating your systems, applications and databases and API-led connectivity is the new way of connecting your business. API-led connectivity comes with a few key advantages that make it an increasingly attractive option when achieving seamless technology delivery across the organization.

Even though automated testing helps you do more software testing in less time with fewer people, maintaining your test suite can be very time-consuming. Many QA teams have a hard time keeping up with maintenance as their product grows. If they fall behind, they get more and more false positives (i.e., cases where the test fails because of a problem with the test, not a problem with the application).

Greetings, my dear readers. It’s been some time since I’ve posted my last article. This is the third chapter of the introduction to the internal data world of Keboola. In the previous chapters, I’ve posted about an introduction to our internal reporting and communication with our users. Since the last time, a couple things have happened.

Kindred Group is a publicly-traded gambling operator with offices across four continents, offering entertainment options such as online poker, sports betting, and online casinos. Since its founding, Kindred has experienced fast growth acquiring nine different gambling brands over the last 20 years. With over 30 million customers globally and numerous brands to manage, the Kindred team had a pressing need for a good data management system.

We have recently launched our disruptive Live Debugger on the Azure Marketplace, making it easier than ever before for teams on the Microsoft stack to slash the time they invest in debugging. We are excited about this, as we have been working closely with Microsoft to make sure that both large international enterprises as well as smaller and scaling startups have direct access to Rookout, to make the most out of our dynamic observability solutions.

There is an urgent need for banks to be nimble and adaptable in the thick of a multitude of industry challenges, ranging from the maze of regulatory compliance, sophisticated criminal activities, rising customer expectations and competition from traditional banks and new digital entrants. As banks find their bearings in this landscape, what appear to be insurmountable odds are in fact opportunities for growth and competitive differentiation.

One of the more challenging aspects of load testing happens very early on: getting your scripts working. When you run your scripts, you may observe unexpected error status codes (typically in the 4xx-5xx status code range). Other times, you'll run your script and see it receive the expected responses (usually HTTP 200), yet the "thing" your script is meant to create simply doesn't show up anywhere, like on the database or as a record on the site. You start wondering: why on earth is that?