AWS Lambda decouples the need to provision and maintain a runtime environment from running code, allowing developers to focus on applications rather than infrastructure. But, by abstracting away the underlying infrastructure of an application, serverless architectures introduce new challenges into monitoring and observability.

At Skeddly we’re focused on bringing you the best in AWS help tutorials, AWS scheduler services, and AWS backup services. However, from time to time we like to reach out to other leaders in the AWS space to help you, our blog readers, stay on top of the latest developments and news within the AWS ecosystem. Today Skeddly had the opportunity to speak with the team at Caserta, a big data and analytics company that helps businesses harness the power data to exceed their business goals.

All developers are not equal, some know how to deploy their applications, others don’t. But now it’s over! With Qovery, all developers can deploy their application in the Cloud in just a few seconds. Qovery integrates seamlessly with Github and requires no effort from the developer. We know how it can be painful for developers to deploy applications, manage staging/development/features environments, synchronize databases and all system stuff - even in the Cloud.

As developers, we need to get back to being diligent - and consistently diligent - about questions of security, provenance, reliability and availability when it comes to packages and dependencies.

Recently, I had a scenario in which it was necessary to access the content of the source JSON message and extract a property that contains a date-time. That property was in the last object (a repeating object) for control purposes, and my first idea was to get it done with Azure Function and that’s it. But then I was thinking, if I need to use Function for all these simple tasks, what’s the point?

For many SREs, networking prompts a similar response as going to the dentist. You know you should do it, but you don’t really want to. But networking is much less like a root canal and more like a regular teeth cleaning; you may not want to go, but once you’re there, it’s not so bad. In fact, you may walk away feeling good knowing that you’ve done something that helps future you.

In a world where organizations store and process more data with each passing year, technology has evolved to keep pace. For example, hard drive capacities have increased steadily and adoption of scalable cloud storage platforms has headed skyward. At the same time, storage vendors have introduced solutions to accelerate storage read and write times — which have historically been a bottleneck in computing.

Is your organization going through a DevOps transformation? Perhaps you’ve even been tasked to head up the project. And surely, part of this transformation is going to include source control management. More and more enterprise companies are using Git to manage their code and file changes. One of the most popular Git hosting services for large teams, particularly those partial to Microsoft’s robust suite of developer tools, is Azure DevOps.

In this blog series, we’ll explore a few different ways that Rancher uses TLS certificates. TLS, or Transport Layer Security, is a cryptographic protocol used to secure network communication. It is the successor to the now-deprecated Secure Sockets Layer, or SSL. You can expect to walk away with an understanding of how TLS integrates into various Rancher components, and how you can prepare your environment to properly leverage TLS in Rancher.

We have made much of why we went with Rancher’s k3s to underpin Civo’s managed Kubernetes service in posts such as Andy’s explanation of k8s vs k3s, but I wanted to take a bit of a deeper dive into k3s and why in particular it is a great technological choice for a service such as ours.