Defining architecture aspects

One of the challenges when evaluating a workload in the cloud is to understand its blueprint and implications regarding the integration between the components. In this sense, the objective of this feature is to deliver a complete blueprint of the architecture, from the infrastructure perspective.

Each resource retrieved by the tool will be classified into different categories:

• Network Layer

• Computing Layer

• Database Layer

• Front-end Layer

• Caching Layer

• Costs Layer

The purpose is to build, customize, and share detailed architecture diagrams of your workloads based on live data from Cloud provider. The benefits of this feature are: Build architecture diagrams, Query Cost & Usage Reports (CURs), Search and classify resources from a functional perspective, Resource directory, Save and export architecture diagrams.

Based on this view of resources, it is possible to establish the general summary of the architecture, as shown below:

• Workload

  • General description of workload, resuming aspects such as: business case, business overview and so forth.

• Criticality of Workload

  • Describe criticality of workload (High, Medium, Low);

• Layers

  • Describe which layers should be evaluated.

    • Computing Layer

    • Database Layer

    • Front-end Layer

    • Caching Layer

    • Services Layer

    • Costs Layer

• Key Performance Indicators

  • Describe which performance related indicators should be evaluated.

    • Computing Layer

      • Computing CPU Use;

      • Computing Memory Use;

      • Computing Network In/Out;

    • Database Layer

      • Database CPU Use;

      • Database Memory Use;

      • Database Network In/Out;

    • Front-end Layer;

      • CDN Response Latency;

      • CDN Invalidations;

    • Caching Layer

      • Caching CPU Use;

      • Caching Memory Use;

      • Caching Network In/Out;

    • Services Layer

      • Endpoint Latency;

      • Service CPU Use;

      • Service Memory Use;

      • Service Network In/Out.

    • Costs Layer

      • Forecast x Executed

• Key Operational Indicators

  • Describe which operational related indicators should be monitored.

    • Computing Layer

      • Computing Status Check;

      • Disk Usage;

    • Database Layer

      • Database Status Check;

      • Disk Usage;

    • Front-end Layer;

      • CDN Status Check;

    • Caching Layer

      • Caching Status Check;

      • Memory User;

    • Services Layer

      • Endpoint Response;

      • Service Status Check.

    • Costs Layer

      • Budget Check