Operations | Monitoring | ITSM | DevOps | Cloud

Today, It's a sad day for thousands of developers that were able to host their applications for free on Heroku. Heroku (acquired by Salesforce) announced that they discontinue their free tier to focus on "mission critical" businesses. Heroku has undoubtedly changed how developers deploy their applications in the cloud - but now, what are the valid alternatives? Here is a list of the top 3 best Heroku alternatives.

2 months ago, I discovered Nixpacks - an alternative to Buildpacks to build a final container image that simply works. I’ve tried it with multiple projects, and the promise is very good. I feel it is less black magic than Buildpacks and easily extensible. In this article, I will share my feedback on the pros and the cons of this emerging project. Let's go!

Since the start of Qovery in 2019, a lot has evolved, the team got bigger, the product grew, a lot of new features were developed, and it’s now time for the pricing to change as well, but don’t worry, I’m not about to tell you that we are increasing our prices because of inflation, we’re just changing our approach in terms of pricing model and let me explain to you how this switch is going to remove plenty of stress from your shoulder!

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 tools for infrastructure automation and monitoring.

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!

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.

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.

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.

It's common practice that development environments for the same product are kept the same (or at least compatible) for smooth software development life cycle (SDLC) workflow. That brings the question, why do we need more than one environment for the same product. In today’s modern software development, it is crucial for product development teams to maintain an effective and rapid workflow if they want to gain a competitive edge in the product market.

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.