Our Blog

We are launching a new series of articles, called Tech Stories, dedicated to the stories behind today's most inspiring companies (and people) about their technology choices, decisions, or new implementations. For the first article in this series, I will relate the DoorDash migration story and give you a closer look at when the engineering team realized they needed to switch, how they operated the switch, and their recommendations for others doing the same. Let’s go!

So you’ve just created a new project and want to start distributing it, but you still don’t know how to manage its deployment. Then there’s the monitoring, network request, and a lot of other problems related to modern apps. At the same time, you want to avoid working directly with AWS due to its intricacy.

Romaric Philogène

CEO & Co-founder

I've used Java as my primary server-side programming language for years. Before joining Qovery, I worked at SAP, where Java was the default choice to bootstrap new projects. Besides its known limitations and cumbersomeness.

Patryk Jeziorowski

Software Engineer

Docker is a high-level virtualization platform that lets you package software as isolated units called containers. Containers are created from images that include everything needed to run the packaged workload, such as executable binaries and dependency libraries. Images are defined in Dockerfiles. These resemble sequential scripts that are executed to assemble an image. Dockerfiles can include several kinds of instructions, such as RUN, to execute a command in the container’s file system, and COPY to add files from your host. In this article, you’ll learn about the key characteristics of Dockerfiles and some best practices to be aware of when you’re writing your own Dockerfiles. Adhering to these guidelines helps you reap the benefits of the containerization movement while minimizing risks in terms of security and performance issues.

Romaric Philogène

CEO & Co-founder

Since the beginning of Kubernetes, a lot of different tools have emerged to manage Kubernetes deployments. They all propose their mindset, workflow, and usage.

Pierre Mavro

CTO & Co-founder

As your number of deployed applications within Kubernetes grows, you may want to isolate them from a network point of view. By default, Kubernetes does not offer any network isolation, all pods of all your namespaces can talk to each other without any isolation, and even on network port that you have not defined. Yes, that's scary! There are different approaches and tools to do network isolation; let's take a look at the NetworkPolicy.

Pierre Mavro

CTO & Co-founder

The AWS Elastic Load Balancing (ELB) automatically distributes your incoming application traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones, ultimately increasing the availability and fault tolerance of your applications. In other words, ELB, as its name implies, is responsible for distributing frontend traffic to backend servers in a balanced manner. ELB monitors the health of its registered targets and routes traffic only to the healthy targets. For example, if a system has only one web server, for system applications with high traffic, long response times or no response will often occur. At this time, you will want to increase the specifications of the web server or increase the number of web servers. If there are two web servers, on which server should the traffic come in? At this time, there must be something responsible for receiving and distributing traffic. That something is ELB.

Romaric Philogène

CEO & Co-founder

Terraform is probably the most used tool to deploy cloud services. It's a fantastic tool, easily usable, with descriptive language (DSL) called HCL, team-oriented, supporting tons of cloud providers, etc. On paper, it's an attractive solution. And it's easy to start delegating more and more responsibilities to Terraform, as it's like a swiss knife; it knows how to perform several kinds of actions against several varieties of technologies.

Pierre Mavro

CTO & Co-founder

The Qovery team is happy to announce that the new documentation website is out!

Romaric Philogène

CEO & Co-founder