One of the most common questions among technology partners and retail clients when facing a deployment, implementation, or technology evolution project is: what infrastructure do I need?
In the past, we made large infrastructure investments, expecting to amortize them over several years. But today’s reality is very different:
- To truly benefit from cloud-based solutions, we must adapt our infrastructure to current needs and keep adjusting over time.
- What works today may not work tomorrow: new technologies, new strategies, and new user experiences demand continuous resource adjustment.
To respond with confidence, at comerzzia we’ve created a technical guide to help analyze the central environment of the Sales Orchestrator, offering a clear view of both current and future needs so you can optimize resources and align your infrastructure with business goals.
This guide does not aim to define specific CPU, memory or storage requirements. Instead, it provides a methodology to identify the key characteristics of each retailer that should be considered to ensure optimal performance, such as:
- Store deployment model (autonomous POS, master-slave, local server).
- Number of stores and use of mobile POS (FastPOS).
- Volume of products, pricing, and promotions, and their update frequency.
- Characteristics and complexity of promotions, and their concurrency.
- Percentage of operations using promotions or loyalty features.
- Use of loyalty apps, including massive campaign pushes via email or notifications.
- Integrations with ERP, ecommerce, BI or AI systems.
- High-demand scenarios (Black Friday, campaigns, returns, cash closings, etc.).
The document expands on these and many other relevant indicators that allow each implementation to be tailored to the real needs of the retailer.
You’ll also find reference environments tested with real clients, including performance benchmarks such as:
- Ticket processing (up to 50,000 per hour with Oracle and Kafka).
- Configuration updates to stores (over 300 million pricing lines in just 2 minutes).
- Simultaneous queries on loyalty data (up to 575 per second).
Why is this important?
Because a proper sizing analysis ensures that the Sales Orchestrator can maintain its performance and availability even under heavy loads, avoiding bottlenecks and degraded user experiences.
Sales Orchestrator Sizing Guide
This document is intended for technical profiles responsible for planning and deploying infrastructure in comerzzia projects. Its goal is to help identify the key factors that influence system performance, scalability, and availability, ensuring smooth operations even under stress.
Want to learn more? Contact our expert team.
