At first, everything is simple: your application uses PostgreSQL, a few users rely on it, and it just works. Then traction kicks in — more users, more data, more queries — and your database starts feeling the weight.
With traditional infrastructure, scaling a database without stopping your application can quickly turn into a technical project: servers, migrations, backups, configuration, maintenance — not exactly where a small team wants to spend its time. With Qeda Cloud, the approach is simpler: you scale your database from your Qeda environment and check that your application keeps running.
In this guide, we'll look at how to scale your PostgreSQL database without downtime.
When should you scale PostgreSQL?
There is no magic number that tells you when to increase resources based on a specific number of users — every application is different. But some signs can alert you:
- your application regularly becomes slower
- response times increase when traffic grows
- your database starts running out of resources
- your data volume grows quickly
- you are preparing a feature that will generate much more data
The idea is simple: scale your infrastructure when your application's needs evolve. You do not need to wait until your database is completely saturated.
A ready-to-use PostgreSQL database with Qeda
If your application uses PostgreSQL on Qeda, you have a database managed from your Qeda environment — you do not need to install PostgreSQL on a server or administer the infrastructure around it yourself. Your application simply uses PostgreSQL as a service, and when it grows, you can scale the resources available to your database.
Before scaling, check your application
Before changing your database resources, take a moment to make sure everything is working normally — no need for a full audit. Simply check:
- that your application works correctly
- that your important data is backed up
- that you can view the status of your database from Qeda
- that your Wallet has enough balance
This is a good habit before making any important infrastructure change. Also keep your Wallet in mind: Qeda works with a prepaid system, and if you increase your database resources, your consumption may also change — make sure you have enough credit in your Billing & Payments page to avoid an interruption caused by Safety Auto-Stop.
Check whether your database really needs more resources
A slow application does not always need a larger database — before scaling, look at what is happening. If your database regularly reaches its limits, increasing its resources may be the right solution. But if it still has enough resources, the issue may come from somewhere else, such as:
- a feature that makes too many queries
- a particularly slow query
- poorly managed data volume
- a lack of caching
The right reflex is simple: look before you increase.
Scale your PostgreSQL database from Qeda
Once you have identified a need for additional resources, open your Qeda environment and select your PostgreSQL database. From your Dashboard, you can scale the resources allocated to it based on the available options — you do not need to manually move your database to another server, or reinstall PostgreSQL. Your application continues to use its database normally.
Does my application stop during this process?
The goal of resource scaling is precisely to avoid turning this operation into service downtime. For a simple resource change supported by your Qeda environment, you can scale your database while keeping your application available. This is the same principle you'll recognize anywhere in Qeda you adjust a service's resources: your change is staged first, with your service still running on its current settings — nothing is applied until you explicitly confirm it.
This is different from a full database migration or a major version upgrade, where additional precautions may be required. But when you simply need to scale the resources of your PostgreSQL database, the goal is to keep the process as smooth as possible.
Check your application after scaling
Once the operation is complete, run a simple test. If your API has a /health route, you can use:
$ curl https://my-api.qeda.app/healthYou can also open your application and perform an action that uses PostgreSQL, such as:
- log in
- display a list
- create a user
- add a product
- create an order
The goal is simple: make sure your application still works normally.
What happens if your application keeps growing?
Scaling once does not mean starting everything over again a few months later. Your application can evolve gradually: you start with a configuration suited to your current needs, then increase resources when your traffic or data volume changes. This is especially useful for a growing SaaS product, a marketplace, a mobile application, an e-commerce platform, an internal tool used by a team, or any application that's starting to handle a lot of data.
The idea is to scale your infrastructure with your product, instead of planning complex infrastructure from day one.
Conclusion
Your application is growing, and your infrastructure can grow with it. With PostgreSQL on Qeda Cloud, you can scale your database resources from your Dashboard without having to manage PostgreSQL servers yourself — you measure, you scale, you verify, and you keep building your product.