Page Comparison

...

These questions are vital to gather the information that affects the following topics in Warren development:

1. 1.  Architectural decisions:
      1. which external libraries, components, and standards to use to cope with the requirements of the majority of DCs in the target group?
      2. How to design the functionality in component systems, so that we provide the value we claim to be offering, without causing the decrease in quality of services and processes existing there before Warren adoption?
   2.  Marketing content and business value:
      1. Can we actually offer the functionality we are claiming to offer?
      2. Can we offer the functionality at a sufficient level of reliability in a particular service domain of a DC?
      3. Are we doing it in a sensible way, e.g. the development effort is comparable to the actual value the development result is providing?
      4. Are all the features and functionality we are/will be providing also in correlation with the actual requirements?

...

Application/Service types

Although, both, this and next point seem to be trivial compared to a real problem magnets like network topology, adopting SDN solution or better yet, consolidating different SDN solutions; this has become a major issue in public clouds (and presumably also in private ones, where such issues are usually not materialized as a series of scientific papers). As Like almost all (except for SDN maybe) network-related considerations, also this one has the quantity-dependent nature. The bigger the amounts of data-flow between hardware devices, the bigger of a problem it tend tends to be.  

In-DC traffic amount between racks

...