Enhancement request for creating multiple Writable Indices per Month for Order Service

Current Order Service (OS) architecture restricts data ingestion to a single writable index per calendar month. Given our high-volume customer requirements of processing upwards of 3 million orders monthly (including sales, returns and purchases)—the index size is projected to exceed the 35GB performance threshold well before the month ends.

Furthermore, the current 17 million record Mass Live Sync backlog cannot be efficiently processed under the "one index per month" constraint without severely degrading search latency and system stability.

Current Bottlenecks & Business Impact

As per current recommendations from IBM OS project team indicate that search performance degrades significantly once an index exceeds 35GB. At a rate of ~65k orders/day (peak exceeding 100k+), we hit this limit mid-month, leading to slow API responses for the end-user. And the Mass Live Sync for 17 million live orders orders is currently unfeasible. Forcing this volume into a single monthly index creates a "Mega-Index" that is difficult to shard, snapshot, or query.

And also the current design does not account for seasonal peaks (e.g., Black Friday/Holiday sales), where a single month's data could be 3–4x the size of a standard month.

Enhancement Request:

To overcome this challenge we request to enhance the OrderService implementation to allow creating multiple write indices in any given month.