🔗 Infrastructure & Environments
General
For us at SCAYLE, the security, availability, and elasticity of our services are top priorities. Therefore, we rely primarily on established best-of-breed technologies that meet our high standards. This includes providers such as AWS, Cloudflare, Datadog, Akamai, and GitLab.
The SCAYLE Engine stack can generally be devided into four layers:
- Edge Services such as Web Application Firewall (WAF) and Content Delivery Network (CDN)
- Compute Services that host our applications
- Storage Services that store data
- Operations Services to manage deployments and monitor our workloads
At the heart of the SCAYLE offering is our SCAYLE Core Engine which is hosted on the managed Kubernetes service AWS EKS. By using AWS EKS as our foundational technology, we ensure the elasticity of our infrastructure while maintaining flexibility in operating it.
The SCAYLE Core Engine utilizes AWS managed databases to ensure fault tolerance and data loss prevention.
Cloud Provider
AWS is our preferred cloud provider and allows us to operate our services globally at scale. We are using many managed services of AWS such as AWS EKS, OpenSearch, ElastiCache, or DynamoDB.
We are operating our services in two main regions of AWS, EU (Ireland) and US (North Virginia). Our services run always redundant across multiple data centers (availability zones) in these regions.
Multi Tenancy
The SCAYLE Core Engine can be structured into two primary layers - the compute layer and the storage layer.
Our application layer is hosted on a multi tenant infrastructure stack where multiple tenants share large Kubernetes clusters. This resource sharing strategy allows us to react fast and efficiently on traffic peaks.
Critical data is always strictly separated between tenants. Each tenant gets their own Database to store sensitive data of their customers. The underlying compute nodes are usually shared as well.
Environments
SCAYLE provides three environments as a default.
Each environment targets a specific use-case.
Live Environment
The live environment is the environment which should be used in production.
This is the environment you have to connect your production Storefront and ERP with. It is set up to achieve high availability and scalability.
It runs with the latest stable version of SCAYLE.
Test Environment
The test environment is intended for use as your primary testing platform. This environment is not designed to handle production-level loads and has some scalability limitations.
It runs the same version of SCAYLE as the 'live' environment.
Preview Environment
The preview environment is the environment which should be used for trying out new upcoming features and test your applications & systems with the upcoming SCAYLE release.
This environment is not meant to be used with production load and comes with some scalability limitations.
It runs with the upcoming version of SCAYLE including the features which will get rolled out to the live & test environment.
Data Replication
The data replication feature enables seamless data transfer between different environments, such as from a preview environment to a live or test environment, or vice versa. This functionality empowers users to configure changes, such as restructuring the Shop Category Tree, in a test environment before pushing the tested setup to production. This practice mitigates the risk of misconfiguration, which could potentially lead to downtimes and revenue loss.
Data Replication Creation
Within the SCAYLE Panel, users can easily select different data sets and transfer them between environments with just a few clicks.
Available Data Sets:
- Translations
- Roles
- Master Categories
- Shop Categories
- Search Configuration
- Pages
- Redirects
- Navigation
- Default Filters
As a security measure, every data replication process requires approval from authorized users. The user interface provides comprehensive insights into the data replication progress, ensuring that users are informed about every step of the process. In the event of any issues, the replication process is automatically halted, and the data is rolled back to ensure the integrity of the system is maintained, preventing any adverse effects.
Rate Limits
Rate limits control the number of requests per unit time.
Each Environment (Live, Test, Preview) has their dedicated rate limit settings.
The Test & Preview Environment are not meant to be used with production load.
In case you want to do some load-tests on those environments, get in touch with your SCAYLE Account Manager beforehand.
General
Rate Limit Scopes
Most API endpoints belong to a rate limit scope such as stockWrite, productRead, etc.
Each scope defines its own rate limit, meaning that there might be no more than X requests within Y minutes to an endpoint of the particular scope.
It is important to note that every rate limit scope is isolated. Moreover, there are usually dedicated scopes for read and write operations. For example, if you have reached the limit by adding new stocks in the system, you can still retrieve stocks for a specific variant.
If the endpoint's scope is not mentioned, the amount of requests is not limited.
Rate limits are the default values, which might vary from tenant to tenant.
Rate Limit Header
Every API response includes the following rate limit related headers:
| Header Parameter | Description |
|---|---|
| X-RateLimit-Scope | The scope to which the endpoint belongs. |
| X-RateLimit-Limit | The total amount of requests that can be made to the endpoint. |
| X-RateLimit-Remaining | The remaining amount of requests, which can be made to the endpoint. |
| X-RateLimit-Reset | The number of seconds until the quota resets. |
Response Example
The response for an exceeded rate limit is as follows:
Live Environment
Admin API - Rate Limits
| Scope | Max attempts / min. |
|---|---|
| customDataRead | 2.000 |
| customDataWrite | 1.000 |
| customersRead | 300 |
| customersWrite | 300 |
| fulfillmentWrite | 300 |
| globalRead | 1.000 |
| globalWrite | 300 |
| ordersRead | 1.000 |
| ordersWrite | 300 |
| pricesRead | 2.500 |
| pricesWrite | 300 |
| productRead | 1.000 |
| productWrite | 300 |
| productSortingWrite | 2.500 |
| shopCategoriesRead | 1.000 |
| shopCategoriesWrite | 300 |
| stocksRead | 2.500 |
| stocksWrite | 2.500 |
| vouchersRead | 300 |
| vouchersWrite | 300 |
To increase rate limits, contact your SCAYLE Account Manager.
Storefront API - Rate Limits
Find all information regarding Storefront API rate limits in our API Guide.
Inform your SCAYLE Account Manager before you expect big traffic events to get an stand-by team for the event.
Test Environment
Admin API - Rate Limits
| Scope | Max attempts / min. |
|---|---|
| customDataRead | 500 |
| customDataWrite | 250 |
| customersRead | 100 |
| customersWrite | 100 |
| fulfillmentWrite | 100 |
| globalRead | 500 |
| globalWrite | 100 |
| ordersRead | 250 |
| ordersWrite | 100 |
| pricesRead | 1.000 |
| pricesWrite | 100 |
| productRead | 500 |
| productWrite | 100 |
| productSortingWrite | 500 |
| shopCategoriesRead | 500 |
| shopCategoriesWrite | 100 |
| stocksRead | 1.000 |
| stocksWrite | 1.000 |
| vouchersRead | 100 |
| vouchersWrite | 100 |
Preview Environment
Admin API - Rate Limits
| Scope | Max attempts / min. |
|---|---|
| customDataRead | 500 |
| customDataWrite | 250 |
| customersRead | 100 |
| customersWrite | 100 |
| fulfillmentWrite | 100 |
| globalRead | 500 |
| globalWrite | 100 |
| ordersRead | 250 |
| ordersWrite | 100 |
| pricesRead | 1.000 |
| pricesWrite | 100 |
| productRead | 500 |
| productWrite | 100 |
| productSortingWrite | 500 |
| shopCategoriesRead | 500 |
| shopCategoriesWrite | 100 |
| stocksRead | 1.000 |
| stocksWrite | 1.000 |
| vouchersRead | 100 |
| vouchersWrite | 100 |
