Blog
Product
4
minutes

New Feature: Instantly Clone Your Service

We're excited to announce the general availability of the new "Clone Service" feature on Qovery, which is built to augment the capabilities of our platform and to cater to our user needs more effectively. Qovery has always prided itself on being a user-centric platform, and this new feature continues to uphold that tradition.
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon

What is the Clone Service Feature?

Up until now, Qovery users were able to clone a complete environment. This feature, one of the most popular, was leveraged by teams who needed to duplicate an environment for testing, benchmarking, demos, sales purposes, and more, without impacting the original environment. It's the Clone Environment feature that is used behind the powerful Preview Environment feature from Qovery.

Today, we've taken it a step further with the ability to clone an individual service from one environment to another, within the same environment, or even within another environment inside another project. That's right, we've lit the 🔥 and amplified the capacity of our platform!

For a detailed understanding of the difference between Clone Service and Clone Environment, we recommend this comprehensive video: Clone Service vs Clone Environment.

How Does the Clone Service Feature Work?

With the Clone Service feature, users can now duplicate a service effortlessly. It smartly clones all the necessary properties, such as environment variables, secrets, resources settings, and advanced settings, ensuring that your duplicated service retains the core of the original. However, it wisely leaves out the settings that cannot be duplicated across services, like the custom domain.

Watch this video to get a quick overview of the Clone Service feature.

Why Clone a Service?

With the Clone Service feature, our users can create replicas of their services instantly, streamlining their workflow and accelerating their development process.

This feature is particularly beneficial when teams need to duplicate a particular service multiple times for various purposes without needing to clone the entire environment. It saves time, improves efficiency, and mitigates risks by allowing users to perform actions on the cloned service without affecting the original one. But here a non-exhaustive list of appropriate use cases for the Clone Service feature:

  1. Individual Service Testing: While Clone Environment is perfect for comprehensive testing, Clone Service allows you to focus solely on a specific service. This approach is not only more efficient but also significantly more cost-effective.
  2. Bug Reproduction and Debugging: Isolating a faulty service by cloning it helps to focus the debugging efforts and reduces the resources needed compared to cloning the entire environment.
  3. Performance Benchmarking: Cloning individual services allows you to tweak and optimize their performance without the overhead costs of duplicating the whole environment.
  4. Demo Purposes: In sales or client demos, you might only need to showcase a specific service. Cloning just this service saves unnecessary expenditure on environment duplication.
  5. Education and Training: Trainees can learn and experiment on a cloned service rather than a full environment, reducing training costs and resource usage.
  6. Microservice Architecture: For applications using a microservice architecture, cloning individual services is significantly more cost-effective than cloning the entire environment.
  7. Environment Cleanliness: Cloning only the necessary services helps keep your environments clean and organized, and is also a more economical use of resources.
  8. Cost-Efficiency: One of the major advantages of the Clone Service feature is its cost-effectiveness. Cloning a whole environment can rack up costs, especially for larger, more complex environments. By allowing users to clone individual services, you can significantly reduce costs while still achieving your objectives.

By bringing the cost-effectiveness of service cloning to the forefront, we've highlighted another significant advantage of the Clone Service feature. Balancing cost with development requirements is crucial, and this feature offers an efficient way to maintain this balance.

The Takeaway

The Clone Service feature is yet another step in Qovery's commitment to facilitating a smooth and efficient development process for our users. It not only broadens the capabilities of our platform but also empowers users to manage their environments and services more flexibly.

We are thrilled to see this feature in action and look forward to hearing your experiences. So, go ahead and start cloning your services, and remember, we're here to assist you every step of the way!

Share on :
Twitter icon
linkedin icon
Ready to rethink the way you do DevOps?
Qovery is a DevOps automation platform that enables organizations to deliver faster and focus on creating great products.
Book a demo

Suggested articles

DevOps
 minutes
The Top 10 Porter Alternatives: Finding a More Flexible DevOps Platform

Looking for a Porter alternative? Discover why Qovery stands out as the #1 choice. Compare features, pros, and cons of the top 10 platforms to simplify your deployment strategy and empower your team.

Mélanie Dallé
Senior Marketing Manager
AWS
Deployment
 minutes
AWS App Runner Alternatives: Top 10 Choices for Effortless Container Deployment

AWS App Runner limits control and locks you into AWS. See the top 10 alternatives, including Qovery, to gain crucial customization, cost efficiency, and multi-cloud flexibility for containerized application deployment.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
 minutes
Kubernetes Management: Best Practices & Tools for Managing Clusters and Optimizing Costs

Master Kubernetes management and cut costs with essential best practices and tools. Learn about security, reliability, autoscaling, GitOps, and FinOps to simplify cluster operations and optimize cloud spending.

Mélanie Dallé
Senior Marketing Manager
AWS
GCP
Azure
Cloud
Business
10
 minutes
10 Best AWS Elastic Beanstalk Alternatives

AWS Elastic Beanstalk is often rigid and slow. This guide details the top 10 Elastic Beanstalk alternatives—including Heroku, Azure App Service, and Qovery—comparing the pros, cons, and ideal use cases for achieving superior flexibility, faster deployments, and better cost control.

Morgan Perry
Co-founder
Kubernetes
DevOps
7
 minutes
Kubernetes Cloud Migration Strategy: Master the Shift, Skip the Disaster

Master your Kubernetes migration strategy with this expert guide. Learn the critical planning phases, mitigate major risks (data, security, dependencies), and see how Qovery simplifies automation and compliance for a fast, successful, and reliable transition.

Morgan Perry
Co-founder
SecurityAndCompliance
DevSecOps
 minutes
Qovery Achieves SOC 2 Type II Compliance

Qovery is officially SOC 2 Type II compliant with an Unqualified Opinion. Get the highest assurance of continuously verified security controls for enterprise-grade application deployments and simplify due diligence.

Pierre Mavro
CTO & Co-founder
Product
Observability
 minutes
Troubleshoot Faster with the New Log Search and Filtering in Qovery Observe

Following the launch of Qovery Observe, we’re progressively adding new capabilities to help you better monitor, debug, and understand your applications. Today, we’re excited to announce a major improvement to the Logs experience: you can now search and filter directly within your application logs.

Alessandro Carrano
Lead Product Manager
Platform Engineering
DevOps
Terraform
7
 minutes
Top 5 Crossplane Alternatives & Competitors

Go beyond Crossplane. Discover Qovery, the #1 DevOps automation tool, and 4 other IaC alternatives (Terraform, Pulumi) for simplified multi-cloud infrastructure management and deployment.

Morgan Perry
Co-founder

It’s time to rethink
the way you do DevOps

Say goodbye to DevOps overhead. Qovery makes infrastructure effortless, giving you full control without the trouble.