What High-Load Support Includes
The scope depends on the project, but support typically covers:
- Speed and stability: regular checks of how fast key pages and services respond, and an investigation of every slowdown.
- Database: tracking slow queries, table growth and indexes, and setting up read replicas when the primary database can't keep up.
- Background processes: making sure imports, email sends and accounting system sync don't take resources away from shoppers.
- Caching and job queues, so heavy operations don't affect visitors.
- Infrastructure: load balancing across servers, Nginx, PHP or Node.js configuration, and headroom for growth.
- Development: new features, library updates and gradual refactoring of problematic code, shipped without taking the live service down.
So you don't hear about outages from your customers, support is usually paired with monitoring and alerts.
Who Needs It and Who Doesn't
The service makes sense for large online stores and marketplaces, portals with user accounts, subscription-based online services, and systems that partners access via API. In other words, anywhere a minute of downtime or a slow page costs real money. Typical signs are a site that is fast at night and slow during the day, crashes during sales, an admin panel that takes minutes to load, and imports that slow down the storefront.
If you have a corporate website or a small store that runs reliably, dedicated high-load support is most likely unnecessary. Standard support with updates and bug fixes will do, and we say so on the first call.
How We Choose Between Optimizing, a Bigger Server and Scaling Out
A more powerful server is the fastest fix, but infrastructure costs go up and the cause of the slowdown stays. Code and database optimization takes analysis and developer time, but it removes the root cause, and the system often handles more on the same resources. Multiple servers give room for years of growth but add complexity. We usually combine approaches: first we clear out the obvious bottlenecks, then plan scaling once the data shows it can't be avoided.
How We Prepare You for Peak Periods
A sale, a major ad launch or a busy season is when an outage costs the most, so we prepare well in advance.
- Together with you, we estimate expected visitors and orders and test that load on a staging copy.
- We reinforce the weak spots the test uncovers and add resources temporarily if needed.
- We move heavy background jobs to overnight hours and agree not to deploy major changes during the promotion.
- We agree on who from the team is on call during the peak and what we do if something goes wrong.
What to Prepare Before We Start
- Access to servers, the code repository, and hosting or cloud dashboards.
- A list of business-critical flows: checkout, payment, account login, warehouse sync.
- A list of integrations and external services the system exchanges data with.
- Incident history: when outages happened, what preceded them and how they were resolved.
- Upcoming plans: expected sales, ad campaigns, expansion into new markets.
If there is no documentation, that is normal: most large projects run without it. We build the picture we need during the audit.
What We Measure and What We Don't Promise
At the start, we agree on metrics and track against them: response time for key pages, error counts, frequency and duration of outages, background process speed, and behavior under peak load. No system runs without ever going down, so we don't promise uninterrupted uptime. Our goal is fewer outages, shorter outages and root causes that don't come back.
What Affects the Cost of Support
- System size and complexity: how many services, databases, integrations and background processes.
- State of the code and infrastructure: whether there is a staging environment, automated deployment, monitoring and documentation.
- Required response time: SLA response during business hours only, or response outside them on individually agreed terms too.
- Development scope: stability only, or new features as well.
- Where the project runs: your own servers, rented servers or the cloud.
We usually start with an audit and then propose an ongoing engagement with a transparent scope of work.
Frequently asked questions
Will you take on a project built by another team? Yes, that is common for large systems. We first get to know the code and infrastructure, and only then make changes.
Do we need to move to the cloud? Not necessarily. The cloud is convenient when load fluctuates a lot, but many large projects run well on rented servers. We decide after analysis.
Can the system be sped up without stopping sales? Yes. We test changes on a staging copy and roll them out to production servers in stages, during the lowest-traffic hours.
What if the system is already going down? Message or call us. In that situation, we first help restore service, then find the cause and propose how to prevent it from happening again.
Do you start with an audit? Yes, usually. The audit maps components, finds bottlenecks and gives you a prioritized plan before we agree on an ongoing engagement.
Do you provide on-call coverage? We respond per SLA during business hours. Outside them, terms are agreed individually, and for sales and campaigns we agree on who is on call in advance.
Why Promodex
Promodex has built and supported websites since 2015 and has 750+ projects behind it, so we know how system requirements change as a business grows. Your code and infrastructure stay with one in-house team that never outsources the work, so there is no split between a developer, a system administrator and a hosting contractor. You see what we do, why, and what it costs.