Environment Details - Bloomreach Experience - Headless Digital Experience Platform

Environment Details

Standard Product Offering

Bloomreach provides access to 1 Production API Endpoint and 1 Staging API Endpoint as part of the standard Search and Merchandising product.
In case you require additional environment endpoints for testing, refer to the Environment Add-On Packages and Pricing section of this document.

Limitations

Production API Endpoint: Bloomreach does not allow load, stress or spike testing in the Production Environment.
If you require such an environment, please see Add-on packages for Performance Test Environment section.

Staging API Endpoint: The primary use of the staging environment is to test all installation, configuration and migration scripts and procedures,before they are applied to the production environment to ensure that all functional aspects of the system works as expected. The staging environment is a close mirror of the production environment, has its own index and ingestion pipeline and will contain the products provided in your product feed.

The staging environment is not intended for any type of Performance or Load testing.

The staging endpoint will be available to you from the beginning of the integration.

Environment Parameters Limits

Max QPS (Queries per second)

10 QPS with max. 10k queries per day

Max # of API requests per day

Max 10k visits / day

Environment Add-on Packages and Pricing

Incremental Staging Environment

The primary use of the staging environment is to test all installations, configurations and migration scripts and procedures, before they are applied to the production environment to ensure that all functional aspects of the system work as expected. The staging environment is a close mirror of the production environment, has its own index and ingestion pipeline and will contain the products provided in your product feed.

Packages

Staging Packages

The staging environment is not intended for any type of Performance or Load testing.

Available Per Year
You would like to have ad-hoc access to an additional Bloomreach staging instance at any given time.
  • Ad hoc access at any time for 365 continuous days

  • Allows search traffic with max. 10 QPS and 10k queries per day

  • You can use your production feed or provide a separate staging feed
  • Product Feed is updated once per day.
  • This environment will be available to you once Bloomreach is able to process and index your feed.

Environment Specification

Environment Parameters Limits

Max QPS (Queries per second)

10 QPS with max. 10k queries per day

Max # of API requests per day

Max 10k visits / day

Peformance Test Environment

The Performance Test Environment is a close mirror of the production environment and can be used for load, stress, soak or spike testing to ensure that the system meets the expected performance criteria.

Packages

Performance Package

Per Week

Per Month

Per Year

You would like to run a one-time load or stress test over a span of 7 or 14 consecutive days. During this timeframe, you want to have ad-hoc access to the performance environment and test a few hours at a given time.

You have a major upcoming release and would like to have ad-hoc access to a Bloomreach load test instance at any given time over a period of a full month (continuous 30 days).

You would like to have ad-hoc access to a Bloomreach load test instance at any given time to be able to do performance test ongoing releases in a year. 

  • Ad hoc access over a period of 7 consecutive days
  • Load test up to 500 QPS max for Search & Categories
  • Load test up to 1000 QPS max for Auto-suggest
  • One time load of product feed
  • Bloomreach will provide data such as # of requests received and average response upon request.

    Requires 5 working days advance notice for Bloomreach
    to get the environment ready and load product data.
  • Ad hoc access over a period of a full month (continuous 30 days)
  • Load test up to 500 QPS max for Search & Categories 
  • Load test up to 1000 QPS max for Auto-suggest
  • One time load of product feed at the initial setup
  • Automated weekly feed refreshes
  • Bloomreach will provide data such as # of requests received and average response upon request.

    Requires 5 working days advance notice for Bloomreach
    to get the environment ready and load product data.
  • Ad hoc access at any time (365 continuous days)
  • Load test up to 500 QPS max for Search & Categories
  • Load test up to 1000 QPS max for Auto-suggest
  • One time load of product feed at the initial setup
  • Automated weekly feed refreshes
  • Bloomreach will provide data such as # of requests received and average response upon request.

    Requires 5 working days advance notice for Bloomreach to get the environment ready and load product data.

Staging Targets

Search, Category and Recommendations Web API, Content Search
Availability Serve APIs with an uptime of 99% per month
Latency Serve APIs with an average latency of 800ms per month      
Dashboard
Availability Uptime of 99% during each calendar month
Connect
Availability of Connect system to ingest feed Uptime of 98.5% during each calendar month
Full feed ingestion jobs for a catalog

Completed within 2 hours

(catalog size < 4,000,000 records)

Delta feed ingestion jobs for a catalog

Completed within 1 hour

(catalog size < 120,000 records)

Limitations

Connect
Full feed ingestion 1 allowed every 24 hours
Delta feed ingestion

1 allowed every 2 hours

Number of attributes supported

17,000 per catalog

Support Staging Targets

Bloomreach offers support services for Bloomreach Search in the Staging environment.  Any errors or abnormal behavior can be reported to Bloomreach Support, who will assign a priority level to incidents reported on the Staging environment based on the table below:

Priority Level

Description

Contact

Target Response Times

(Premium Support)

P2

Issues that are having an impact on testing a change for validation, or a release such as Bloomreach Staging API being not responsive

[email protected]

 

24 hours

24x5

P3

Non-critical issues, where there is no direct impact on the testing, but the user experience is not optimal. 

[email protected]

 

48 hours

24x5

Note 1: All Testing has to be done within the bounds of the capacity provisioned for the environment. 

Note 2: Our targets on the Staging environment expect your Staging configurations to be the same as your Production Environment. No targets can be associated if there are changes made especially in the product catalog data being indexed that varies from production.

Note 3: Response time is not the same as resolution time. The resolution time will be shared with you by your support POC.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?