Услуга · Cloud services and hosting

A server for 1C-Bitrix

The platform makes very specific demands of its environment, and on cheap shared hosting it runs slowly while exchange with accounting breaks off halfway through an upload. We build the environment for it correctly from the start.

Test
brought up to a high score
Cache
tuned to your traffic
Uploads
run through to the end
Copies
files and database separately

What the work includes

The quirks of the platform are known and well documented, so the environment is prepared for them in advance rather than reworked after complaints.

Discuss the scope

Components

The versions the platform considers recommended, with parameters dialled in.

Built-in test

The built-in check must return a high score, otherwise talking about speed makes no sense.

Acceleration

Cache, a code accelerator, sessions moved out - so the site holds up under a rush of visitors.

Exchange with accounting

We lift the time and memory limits that stop large uploads from completing.

Copies

Files and database are copied separately, and one instance is kept off the server.

Protection

Restricted access to the admin area, regular updates, a filter against common attacks.

How it goes

The environment is built in a day; moving a live site takes one to three days including checks.

01

Costing

We size resources by traffic, catalogue volume and exchange frequency.

02

Build

We deploy the environment and get a decent result from the built-in check.

03

Migration

We move files, database, domain and certificate, then switch over at the quietest hour of the day.

04

Check

We look at speed under load, a full exchange cycle, checkout and the admin area.

Caching speeds a site up right until someone turns it off in the panel. A developer disables it for edits and forgets to switch it back - the site becomes three times slower for no visible reason. Check the cache state every time you look into complaints about speed.

Questions and answers

Most often the issue is not capacity but settings: caching switched off, slow disks, poor database parameters. The built-in test of the platform shows this in a minute and saves you from pointlessly adding cores.

With a catalogue of up to a few thousand items and moderate traffic - no, everything lives happily on one machine. Splitting pays off on large shops where the database and the web part start competing for memory.

The database daily, files daily or every other day, since they change less often. For a shop with active sales it makes sense to copy the database more frequently, because losing even a few hours of orders is felt.

We will prepare the ground for the platform

Describe the site: catalogue size, traffic, whether it exchanges with accounting. We will pick resources and move it without downtime.