Our Blog

I am pleased to interview Oliver Juhl, CTO and co-founder of Medusa - an open-source headless commerce platform.

Yesterday was my worst day for a very long time. We spent so much time promoting our Qovery Engine to the open-source community and getting those ~3800 stars. I woke up and discovered that we had lost all the stars and forks from our repository. But what happened?

Romaric Philogène

CEO & Co-founder

We are pleased to interview Quentin De Quelen, CEO and co-founder at MeiliSearch - an open-source search engine written in Rust.

Making an Open Source Software with sensitive data and dozens of external integrations is a real challenge, here are feedbacks and tradeoffs we've made.

Pierre Mavro

CTO & Co-founder

This is the most exciting feature we launched since Qovery v2 has been released - the Preview Environment feature!

Romaric Philogène

CEO & Co-founder

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