Architecture analysis framework

For Architecture Analysis Tenendo experts use AWS Well-Architected framework.

AWS Well-Architected helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for a variety of applications and workloads. Built around six pillars — operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability — AWS Well-Architected provides a consistent approach for customers and partners to evaluate architectures and implement scalable designs.

Technical Audit approach

The audit is split into two parallel streams: Architectural analysis and Performance testing.

Architectural work: Technical infrastructure setup review and analysis, scalability analysis and performance model development, attending the Performance test plan preparation, performance test results analysis.

Performance testing work: Performance test plan preparation, scenarios preparation, test environment configuration, test data generation, test results analysis, test scenarios source code packaging, Performance testing report preparation. 

Performance testing is used to assess the current performance of the system, analyse the behaviour of the system in case of service timeout or denial of service and predict the necessary changes in the architecture of the system. Testing is carried out iteratively for 100, 400, 1000, 10000,… users.

Who performs the technical audit?

Cloud architect performs infrastructure setup review and analysis, scalability analysis and performance model development, attending the Performance test plan preparation, performance test results analysis.

Performance testing engineer performs Test plan preparation, scenarios preparation, test environment configuration, test data generation, test results analysis, test scenarios source code packaging, testing report.

Performance/Capability goals examples

  1. The average response time (measured by the time to last byte metric) is less than [3] seconds
  2. The worst response time (measured by the time to stay byte metric) is less than [10] seconds
  3. The average CPU utilisation of the database server is less than 75%
  4. The average CPU utilisation of the application server is less than 75%
  5. Each server must be capable of handling [1000] concurrent users
  6. The maximum number of acceptable server errors, non-HTTP-200 status codes on client requests, will be less than 2% of all client requests.

Approach and Execution Strategy

  • Software is tested independently of an existing testing process.
  • Tenendo experts create Test Plan, which serves the Testing Team’s basis for creating test scripts.
  • The Testing Team runs scripts using the existing test framework.
  • The Testing Team watches and measures the front-end, backend, and RDS CPU utilisation during testing.
  • After the performance test cycle, the Testing Team analyses and presents the results to stakeholders.

Technical Audit deliverables

Test Plan – a document detailing the objectives, resources, and processes for Performance testing

Test Scripts – A testing framework with test scripts for continuous use in your CI/CD pipeline.

Test Results Data – Accurate performance data resulting from our performance tests

Test Report – The final report that documents and summarises the results of performance tests that were conducted according to the test plan.

Technical Audit Final Report – The final report that documents and analyses the current cloud infrastructure setup, potential issues as shown by the performance test, expert improvements and recommendations.