Operations | Monitoring | ITSM | DevOps | Cloud

One of the most exciting things when using Kubernetes is the ability to scale up and down the number of nodes based on application consumption. So you don’t have to manually add and remove nodes on demand and let it go on usage. Obviously what you want is to keep control on the minimum and the maximum number of nodes to avoid an unexpected bill.

When building serverless applications on AWS Lambda, Amazon CloudWatch provides out-of-the-box metrics that measure the performance, errors, and duration of your functions. Although these standard Lambda metrics provide visibility into your serverless applications, it can also be invaluable to monitor custom metrics that are unique to your use case and application.

The second quarter is now over and after the start of our V3 at the beginning of this quarter we are super happy to announce that it’s now out in Alpha but there is so much more to speak about so without further due, let me show you all the great things we achieve during the past quarter 🚀

The first continuous integration (CI) tools were all self-hosted, meaning they ran on a developer’s local computer or server. Although this setup was viewed favorably by dev teams at the time, it has limited flexibility, and developers had to spend time maintaining the infrastructure.

Modern application deployments rely heavily on containerization for its scalability, availability and ease of maintenance. Legacy applications implemented before the containerization era often use monolithic, hardware-centric architectures that are difficult to scale and manage. These legacy applications may have multiple services bundled into the same deployment unit without a logical grouping.

Ciara details how and when to generate an SBoM with the help of open-source tooling. Learn how to host SBoMs, as well as other SBoM considerations.

Developers today need to build software from many platforms in order to reach their users. All while maintaining quality and achieving the best user experience possible. This can be a challenging task when you need to meet the growing needs of software development. This is where the Dart and Flutter come into the picture.

Service level objectives (SLOs) state your team’s goals for maintaining the reliability of your services. Adopting SLOs is an SRE best practice because it can help you ensure that your services perform well and consistently deliver value to users. But to gain the greatest benefit from your SLOs, you need ongoing visibility into how well your services are performing relative to your objectives.

Today, we’re excited to announce the release of Cycle’s new pricing model! With this new model, we aim to make our pricing far more straightforward and better suited for larger deployments and customers. While our current pricing model solved the needs of our customers for the last few years, we’ve learned enough that it’s now time to make a change. Before talking about the new model, let’s dive into how we got here.

Multi-cloud strategy – the use of multiple private or public clouds – is increasingly becoming the main method companies use to deploy their IT infrastructure. In the next three years, an estimate 64% of companies will rely on multi-cloud as their main deployment model source. Despite the complexities that come from operationalizing it, as we disccussed in The Challenges of Building Multi Cloud, the multiple benefits that come from this deployment model can often make it worth the effort.