Operations | Monitoring | ITSM | DevOps | Cloud

Aiven contributes back to the Apache Kafka® community with a dedicated full-time team. Find out more about our work!

Today, almost every IT department or MSP uses some form of mobile technology. Even though smartphones, laptops, tablets, and other mobile endpoints are incredibly useful for an organization, they can be difficult to manage. TechFunnel’s article on mobile devices in the workplace announces that one laptop is stolen every 53 seconds, while 7 million smartphones are lost every year.

Properly testing a service’s APIs to ensure that it can handle production traffic presents many challenges for engineers—SREs need to guarantee the resiliency of their application, while developers must ensure that their features perform well at any given scale. Speedscale is a testing framework built for Kubernetes applications that enables you to load test with real-world production scenarios by replaying actual API traffic that your application has experienced.

An API is an important feature to look for when it comes to making cloud purchasing decisions. Here's why.

Load testing is one of the most common ways to test the resiliency of your applications. In this blog we show how recording production data with Speedscale and exporting to a K6 load tests gives you the best of both worlds. Whether or not it’s important for your organization, there are clear benefits to be had from implementing these types of tests. By doing so, you can: When it comes to load testing, two of the most modern tools are Speedscale and K6.

RAN has incrementally evolved with every generation of mobile telecommunications, thus enabling faster data transfers between user devices and core networks. The amount of data has increased more than ever with an increase in the number of interlinked devices. With existing network architectures, challenges lie in handling increasing workloads with the ability to process, analyse and transfer data faster. The 5G ecosystem requires virtual implementations of RAN.

Content management is shifting toward two headless options: Git-based and API-driven. Headless CMS solutions allow developers to edit and manage content easily while still using the front- and back-end tools and platforms they know and love. These Git-based and API-driven CMS solutions give developers a new way to expedite CI/CD processes without compromising product quality. Git is an essential tool for both beginners and seasoned software developers.

Back in 2020, we covered the launch of Lambda Extensions and the subsequent release of the Lambda Logs API. These features aren’t designed for the average Lambda user. But they allow vendors to build better tools by giving them much-needed access to the Lambda execution environment.