Do you know what size server you want for your eCommerce site?Pradip Shah
Leaving the toughest question unanswered
When signing up for your Magento hosting, the first question you see asked, before you place an order, is what size server you want. It has become so ubiquitous, that everyone just expects to answer it looking at the cost.
But this is much like Mathematics books leaving tough problems as exercise to the readers!
It should not be that way! The size and architecture of the server you need depends on many factors.
Factors to consider
- The traffic and pattern. We routinely ask for 2 google analytics graphs – one for a typical day and one for a high sale day. This drives the architecture and server size.
- Your hosting stack – are you vanilla magento? or do you use headless / PWA? or use some software for image optimisation on your server?
- If the live site is already hosted, current CPU and memory usage.
- The size of the magento database.
luroConnect always starts an engagement with a server sizing sheet that is filled on behalf of the merchant. This allows us to propose a hosting plan on the customers cloud account and an appopriate luroConnect support plan.
Server Architecture anybody?
Most hosting providers are interested in selling you servers. The actual implementation of the architecture is again left as an exercise to you.
Magento is best implemented in a classic 3-tier architecture.
- The web layer (WAF, apache / nginx /varnish, cron, rabbitmq),
- the application layer (php, nodejs) and
- the database layer (mysql, elasticsearch, redis).
This architecture has some advantages :
- app servers can scale independently – indeed they can be autoscaled.
- Low traffic websites can fold either the app or the db layers or both into the web layer
- The db layer can be extended to have master slave
- A proxy layer can load balance read traffic between master and slave, giving scalability at the database level