...

1. 1.  Architectural Decisions:
      1. Which external libraries, components and standards to use to meet the requirements of the majority of DCs in Warren's client target groups. 
      2. How How to architect features across components, to provide value Warren aims to offer, while maintaining quality of services and maintaining necessary processes the DC had before adopting Warren. 
   2.  Business Value and Marketing:
      1. Can Warren guarantee to offer the functionality we are claiming to offer?
      2. Can Warren provide the functionality at a sufficient level of reliability in a particular domain of service for the DC?
      3. Will development effort for Warren be in proportion to the business value the developed functionality is forecasted to provide?  
      4. Are/will features and functionality of Warren be in correlation with the actual requirements of the DC?

Conflicting nature in service requirements

...

Trade-Offs between Availability vs Locality and Software vs Hardware Defined control

There are two fundamental tradeoffs that a DC needs to decide on:

• Availability vs Locality
• Software vs Hardware-Defined control

To analyze the possible tradeoff decisions for a DC and to make the input directly usable in Warren's development process, the hypothetical DC stack is divided into the following functional domains: hardware, firmware, software. All three domains have common properties that correlate to Warrens software components. Stack for Network and Storage that the DC has previously adopted define the biggest influence in future developments and technical on-boarding.

Network and Storage are tightly coupled, as decisions in one domain heavily depend on are influenced by the properties of the other domain. If analyzed, the Once the connection between these two domains is expressed best in the decision-making process, as two fundamental trade-offs - availability vs locality and software- vs hardware-defined domains of control.Network and Storage domains are analysed in full, decision-making in the following two trade-offs is possible. 

Availability vs Locality

 The biggest trade-off there decision is in multi-site location computing, (thus - distributed cash cache and storage are simultaneously good and evil at the same time evil ). 

1. Availability in this context denotes:
   1. Spacial continuity - data or service is concurrently available to recipients/consumers in different locations rather than just one (one 
      Example: many Virtual Machines using the same database that resides in distributed storage)
   2. Temporal continuity - data or service is kept available even in case of soft- or hardware failures ("High Availability")
   
   Both of these aspects In cloud computing both spacial and temporal continuity may seem very desirable, especially in cloud computing, but the downside is delivery speed in various formsand latency. For example , spacial availability with distributed storage without high-end hardware may not have sufficient the optimal latency for storage-sensitive applications. Also, to keep the application availability rate high, there are software and several levels of hardware redundancy involved which means buying additional devices and keep them constantly running.
   Locality  To assure application high-availability several software and hardware redundancies are involved. This requires buying and maintaining additional hardware, which makes the Total Cost of Ownership higher. 
   
   
2. Locality (local storage vs distributed storage) denotes the physical distance of some a functional domain from compute resource (local storage vs distributed storage)resources. 
   
   While High Availability metrics are received by involving distributed and redundant resources, the locality is also not free from redundancy cost, however, it is usually the one of sub-server level, so definitely less expensive. Local storage has also much lower latency, but total capacity is very limited; and, as data on this storage is not available to outer devices without additional control and services, it introduces additional data duplication demand besides the one meant for "High Availability".

...