As you’ve probably realized by now, cloud computing isn’t the future. It is here and now. According to Gartner, global spending on public cloud services alone will surpass $725 billion by 2024. This rise in cloud computing is a great career opportunity for you. And what better way to immensely benefit from this shift than becoming a cloud engineer?

Imagine a central hub where your tech team finds all the tools and resources they need, organized and ready for action. This is exactly what the Internal Developer Portal offers, becoming a key factor in revolutionizing the way we build software today. In this article, we will explore how Internal Developer Portals revolutionize the development process by streamlining tasks, boosting collaboration, and customizing workflows.

I am thrilled to announce a significant milestone for Qovery: the public beta release of our Google Cloud Platform (GCP) GKE Autopilot support. This marks a new chapter in our journey, following the successful integration with AWS EKS, Scaleway Kapsule, and Kubernetes. In this announcement article I'll explain what you can get out of GCP GKE Autopilot and what is coming next 👇

Contributing to open source software helps you develop new skills, gain real-world coding experience, interact with new technologies, and meet new people. But with so many open source projects to choose from — developers started some 52 million new projects on GitHub in 2022 alone — it can be difficult to figure out which repositories to contribute to. If you’re thinking about joining a new open source project in 2024, you’ve come to the right place.

Observability, in modern software engineering, has evolved into a paramount concept, shedding light on the intricate inner workings of complex systems. Three essential pillars support this quest for clarity: logging, traces, and metrics. These interconnected elements collectively form the backbone of observability, enabling us to understand our software as never before. Think of a system as a bustling city.

In the latest instalment of our interviews speaking to leaders throughout the world of tech, we’ve welcomed Chris Campbell, CIO at DeVry University.

As on-premises infrastructure and workloads increasingly migrate to the cloud, you’ve undoubtedly encountered many challenges in managing complex cloud architectures. These hurdles include juggling cost-efficiency and security to maintain a seamless, high-performance infrastructure. Navigating your cloud infrastructure landscape requires thoroughly understanding its virtualized elements—servers, software, network devices, and storage.

As we’ve seen throughout this series, a design pattern is a general solution that has been proven to solve a repeatedly occurring problem when designing software. In my previous blog posts, we examined the basics of the software operator design pattern, the forces impacting it, and the advantages and disadvantages of using it. But how does the software operator pattern actually work?

Moving to Teams Phone as your primary voice system can save money and provide a great user experience, or it can “crash and burn”. In a two-part workshop, I had the opportunity to explore insights to help migrate successfully to Teams Phone with Greg Zweig of Ribbon. (Ribbon was kind enough to sponsor both workshop sessions.) This article summarizes the information we covered in the workshop.

In the ever-evolving landscape of software development and IT operations, monitoring tools play a pivotal role in ensuring the performance, reliability, and availability of your applications. Two key disciplines in this domain are observability and Application Performance Management (APM). This post will help you understand the nuances between observability and APM, exploring their unique characteristics, similarities, benefits and differences.