Our Blog

Application containerization has disrupted the way software applications have been built and deployed. Over the years, Kubernetes has stood out as one of the best platforms for container orchestration. It has helped many companies achieve scalability, resilience, portability, and better resource utilization in their products. However, managing Kubernetes is still complex. The first question which comes to mind is whether we should use a single cluster or a multi-cluster for Kubernetes. Although a single cluster is easy to set up and manage and provides the basic features of Kubernetes, it lacks the typical resilience and high availability Kubernetes is famous for. In many cases, a single cluster is not enough to manage the load efficiently across all components. As a result, we need more than one cluster for a better division of workload and resources, hence the need for a multi-cluster solution. In this article, we will discuss in detail multi-cluster Kubernetes, why it is used, and when we should prefer it over single-cluster.

Morgan Perry

Co-founder

You must adopt proper infrastructure automation if you want to enable your teams to achieve faster application delivery while eliminating human errors. Automation of servers, deployment environments, configuration management, and deployments play a vital role in getting a competitive advantage for your product. Monitoring both the infrastructure and application is equally important as well. In this article, we will discuss top DevOps Automation tools for infrastructure automation and monitoring.

Morgan Perry

Co-founder

Since our start in 2019, we are proud to say that a hundred engineering teams from fast-growing organizations trust us to deploy their Production, Staging, and Development Environments on AWS in a few seconds. But why do they use Qovery, and how? That’s what you’re about to discover today!

Albane Tonnellier

Product Marketing Manager

When you build a SPA product one of your first preoccupations is to keep everything fast. You click, and you get instantly a feedback. If you click on a link, you want to navigate instantly to the desired page. If when you click you have to wait for some time before feedback, the user experience quickly becomes horrible.

Benjamin Debon

Software Engineer

This September 6, 7, and 8, the Developer Week Cloud conference will take place in the Palmer Events Center, Austin, TX, and guess what? Qovery will be there! 🚀

Albane Tonnellier

Product Marketing Manager

If you are part of a DevOps or Cloud engineering team struggling to set up and maintain proper environments, then this article is for you. We will discuss “On-demand” environments in detail. We will go through its benefits, how development teams can take advantage of it, and how Qovery’s on-demand environments give you a competitive advantage in the business.

Morgan Perry

Co-founder

Albane here, Product Marketing Manager at Qovery 👋🏻 Yesterday we joined forced Pierre Olive (CTO and co-founder of Spayr) to talk about how they manage multiple environments on Kubernetes with Qovery and much more; if you missed it or would just rather read than listen, here is the recap.

Albane Tonnellier

Product Marketing Manager

Qovery V3, which is the most significant product evolution of the last twelve months, was launched in Alpha testing about two weeks ago now. We started gathering some feedback and also added some new functionality since then so let’s take a look on how’s going.

Albane Tonnellier

Product Marketing Manager

Consider the scenario where a complex product is being developed by dozens of engineers working on different features of a product. Not only the development environment is the same, but the staging environment is also shared. As different features are merged into the shared environment, they break the code. So QA has to wait until this is fixed. A feature or bug fix may be working perfectly on the developer’s own machine, but there is no way for the QA team to test that one feature in isolation. This problem is intensified when the product has a lot of integrations and different data sources. The DevOps team simply cannot provision so many different environments on time; they will miss the bus. If developers keep using the same shared staging environment, it will take ages to deliver a mature product to the market. This is where the concept of preview environments comes into play. In this article, we will tell you what preview environments are and how they solve the above problems. We will also discuss why so many DevOps teams are adopting it to improve team productivity.

Morgan Perry

Co-founder