As a developer, using Heroku (a Platform as a service (PaaS)) helps get our applications up and running quickly. Without worrying about servers, scaling, backup, network, and so many underground details. Heroku is the perfect solution to start a project. But as the project grows, the needs become more complex, and moving from Heroku to Amazon Web Services (AWS) becomes more and more a no-brainer choice (discover why so many CTOs decide to move from Heroku to AWS).

TLDR; Pleco is a service that automatically removes Cloud managed services and Kubernetes resources based on tags with TTL. When using cloud provider services, whether using UI or Terraform, you usually have to create many resources (users, VPCs, virtual machines, clusters, etc...) to host and expose an application to the outside world. When using Terraform, sometimes, the deployment will not go as planned.

The high demand to deliver software that is both highly available and able to meet customer requests has, in part, led to the adoption of microservice architecture, a software architecture pattern that makes it easier to deploy applications as self-contained entities called containers. These containers are nothing but processes that run as long as the application in them is running.

2021 has been a crazy year for the Qovery team. When I look back, 1 year ago we were 4 in the team, now we are 15! We expect to double the size of the team for 2022 while keeping our developer DNA. 2022 looks bright, and we strive to make the cloud simple for everyone.

Heroku is a cloud-based platform that helps companies build, deliver, monitor, and scale applications with high velocity. Heroku's popularity is due to its simplicity, usability, elegance, and focus on the developer experience. Developers find Heroku helpful as they can get their application ready and running with only minimal focus on configuring infrastructure. Heroku scores on easiness in architecting apps, deploying them to flexible cloud infrastructure, and scaling them as required.

So you’ve heard of Kubernetes, and you’ve decided it’s time to dive into what everyone’s talking about. Or maybe you’ve worked with it a little, but you’d like to level up.

Traditionally, provisioning an infrastructure meant a team of field engineers, system admins, storage admins, backup admins, and an application team would all provision and maintain an on-premises data center. Although this system works, it has a few flaws—slow deployment, high cost of setup and maintenance, limited automation, human error, inconsistency, and the underutilization of resources during off-peak periods.

I am super excited to announce that our Preview Environment feature is GA (Globally Available) for everyone 🥳.

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?