Hardware Sizing Guidelines
You must consider certain non-functional requirements when designing infrastructure topography. You also have to follow specific guidelines before making hardware recommendations to a customer.
An example of a non-functional requirement involves putting logging and operational Enterprise Message Service (EMS) traffic on the same Enterprise Message Service instance. However, this leads to delays in processing orders because the orders are blocked by non-business critical logging traffic. A better solution is to create separate Enterprise Message Service instances for logging and core Enterprise Message Service traffic to eliminate this blockage.
Hardware sizing is generally an outcome from preliminary performance testing. All environments are different, and you cannot use a cookbook approach to a particular order management problem. It is a good practice to complete extensive performance testing on lab hardware before recommending particular hardware to a customer. These lab runs must reflect a realistic order size, load mix, and anticipated plan size. The plan must also cover pre-submit and post-submit activities, in particular, validation and eligibility calls to Offer and Price Engine (OPE).