IT architecture audit

The architecture of your systems is too important to rely on only own assessment.

audyt


Choose an audit

first

Transition to microservices

second

Second architectural opinion

three

Diagnosis of performance

arrow
Purpose of the audit
Assessing the system’s readiness for transition to microservices architecture.
Independent experts’ opinion on the architectural concept.
Assessing applications from the perspective of supporting planned business growth (of the number of users, transactions, queries etc.)
arrow
What problem audit solve?
Presenting potential benefits from migration and an initial action plan.
Early discovery of problems and areas requiring improvement.
Identifying performance bottlenecks and presenting suggested improvements.
arrow
System*
Middle-sized
(up to 500,000 lines of code)
Middle-sized
(up to 500,000 lines of code)
Middle-sized
(up to 500,000 lines of code)
arrow
Scope of audit
1. Domain complexity
2. Degree of modularization of the existing code
3. Technological debt
4. Test coverage
5. Automating the CI/CD process.
1. Solution’s scalability
2. Modularity and openness for changes
3. Development process
4. Deployment process
5. Applied technologies from the perspective of correctness and validity of their use.
1. Conducting performance tests: capacity tests, stress tests, soak tests
2.  Analyzing the solution’s scalability and applied technologies for correctness and validity of their use.
arrow
Scope of report for the Client
Objective assessment of the solution’s architecture in the analyzed areas from items 1-5.
Proposed migration plan (if the readiness level allows it).
Objective assessment of the solution’s architecture in the analyzed areas from items 1-5.
Recommending optimizations in accordance with the indicated architectural drivers (performance, availability, security, privacy, disaster recovery, UX & accessibility, auditability, flexibility, extensibility, maintainability, portability, internalization etc).
Results of the listed types of performance tests.
Recommending optimizations – identifying the solution’s elements which cause problems, and proposing optimizations.
arrow
Our requirements
Insight into the system’s technical documentation.
Access to the system’s runtime environments.
Access to the main architect of the system or another competent person.
Insight into the concept’s documentation.
Access to the main architect of the system or another competent person.
Insight into technical documentation.
Access to the system’s runtime environments.
Access to the main architect of the system or another competent person.
arrow
Lead time
3–5 days
3–5 days
3–5 days
arrow
Auditor’s competences
System architect with at least 5 years of experience in designing and implementing enterprise-class systems. Experience in working with international projects and teams.
System architect with at least 5 years of experience in designing and implementing enterprise-class systems. Experience in working with international projects and teams.
System architect with at least 5 years of experience in designing and implementing enterprise-class systems. Experience in working with international projects and teams.

* Depending on the system’s complexity, lead time and price may be subject to change.

** Applies to work in the remote model. If the service is provided at the Client’s location, the cost of transport and accommodation is added.

Please provide us some additional information. This will allow us to better respond to your needs and match the audit offer.

The purpose of the audit / audited system/ technologies
First and last name
E-mail (required)
Phone number (required)
(i) Consent to personal data processing