Architecture

The architecture

Traditional hosting

One central location

VisitorCentral server

Every visitor goes to the same server, wherever they are. The further away, the longer the route.

Serverless

The nearest location

VisitorEdge location

Not everything sits in one central point. Each visitor is served from the edge location closest to them.

PHP platform

A stack of services on a server

VisitorServer you manageWeb serverPHPDatabaseCacheSearch serverCron & queuesoperating system · patches · capacity

A PHP platform such as Magento runs on servers with a web server, PHP, a database, cache and a search server. That gives a lot of freedom for custom work, but someone has to manage, patch and scale that stack.

Serverless platform

Code and database, without a server stack

VisitorWorkercode at the edgeDatabaseof the webshopincl. searchMedia storage

On our serverless platform the code runs as a Worker at the edge. Each webshop has one database of its own, which also holds the search function, plus media storage. There is no operating system, PHP version or separate service to manage.

PHP platform

Starting up on every request

On every requestRequest comes inPHP process startsLoad framework and codeRun code → response…and again for the next request

PHP code sits on the server as separate files. On every request a PHP process starts and loads the framework and the code before the actual work begins. Caches such as OPcache shorten that, but the start-up happens again for each request.

Serverless platform

Compile once, then only run

On every release · onceSource codeTypeScriptCompileinto one bundleDeployto the edgeOn every requestRequestIsolaterun the bundleResponseno server or framework to start up

With us, the code is compiled in advance into one bundle on every release and deployed to the edge locations. A request runs that bundle directly in a lightweight isolate: no container or virtual machine that has to start up first.

The code runs on the edge location closest to the visitor. A webshop's data lives in that webshop's own database:

Visitor Edge network Worker Media storage Webshop A own database Webshop B own database Webshop C own database

Runs on Cloudflare's edge network

The code runs on Cloudflare Workers, close to the visitor. There is no server to rent, patch or manage.

One database per webshop

Every webshop has its own database, physically separate from the others. No query can reach another shop: it is not there. A busy shop does not slow down the others.

Stock and orders in one transaction

Stock, basket and orders live in the same database of the shop, so an order updates the stock in the same transaction.

SSL, DDoS protection and CDN included

On Cloudflare's network, with a custom domain per webshop.

Tested at scale

Tested with a catalogue of 70,000 products and 130,000 variants.

Your data stays yours

Products, orders and customers can be exported as standard CSV. Passwords are stored only as a hash.

Routes

Three routes,
one team

Magento 2 & Hyvä

Custom Magento

Have your Magento 2 webshop built, sped up and managed by a Magento specialist active since 2010.

More about Magento
Magento SaaS

Cloudgento

Magento as a fully managed SaaS solution on our own platform.

Discover Cloudgento
Own platform Coming soon

Serverless SaaS

New platform of our own, coming soon. Separate from Magento, with no servers to manage.

Magento remains the core of our work; the serverless platform is an addition, not a replacement.

FAQ

Frequently asked
questions

Other questions? We always respond within one working day.

Ask your question

No, it is WEBSHOT's own platform, separate from Magento.

Soon; no date has been published yet.

No. Magento remains the core of our work; the serverless platform is an addition, not a replacement.

Yes, via the contact form.

Status

The platform is
in development

The platform is in development. We will announce features, prices and the launch date at release.