Certificate of Hard&Soft Skills
]
[
This certificate confirms that
Aliaksei Sauta
successfully completed the course «Solution Architect in the Wild»
lasting 12 weeks
Aliaksei Sauta
successfully completed the course «Solution Architect in the Wild»
lasting 12 weeks
Teachers of The Course
]
[
Principal Solution Architect
Anton Dvornikov
Developer since 2000, has worked as a developer, team lead, and architect in product companies.
Built architecture and processes for a product involving a dozen teams, 200+ engineers, and microservices.
Currently building architecture and processes for a system with several thousand services.
Built architecture and processes for a product involving a dozen teams, 200+ engineers, and microservices.
Currently building architecture and processes for a system with several thousand services.
Developer since 2003, has been teaching since 2008, training seniors and architects since 2018. He has shared expertise in more than 100 meetups and conferences.
Pavel is one of the founders of various communities of IT specialists, including ByChange, Free IT. He perfomed the roles of developer, team lead, architect, CTO in small startups, large corporations and product companies.
Trained more than 1K developers over the past 15 years, including over 200 architects. Creates educational courses for many technical areas.
Specializations: distributed systems architecture, highload, microservice architectures, systems engineering, engineer growth, corporate communication.
- Architect: Miro, EPAM
- CTO: AmadoAd Ltd., SplitMetrics, Leverice
- Tech Advisor: LeoHome Inc.
Trained more than 1K developers over the past 15 years, including over 200 architects. Creates educational courses for many technical areas.
Specializations: distributed systems architecture, highload, microservice architectures, systems engineering, engineer growth, corporate communication.
Founding Teacher at Hard&Soft Skills
Pavel Veinik
The course programme included:
]
[
Module 1. The Beautiful Theory of Solution Architecture
1. Architecture and the Architect
- What is architecture? Why is architecture important?
- Architectural contexts
- Types of architects, roles of a Solution Architect and an Enterprise Architect
- Methodologies: TOGAF, Zachman, FEAF. Choosing the right framework and applying it in practice
2. Business Architecture
- Value stream: How does a business create value, and why is it important for an architect?
- Business motivation: Business drivers, goals, objectives
- Stakeholder management: Identifying stakeholders, types of stakeholders, their interests. Power-Interest matrix. Practices for resolving conflicts
3. Requirements
- Functional requirements
- Non-functional requirements, assumptions. Architecture Significant Requirements, Constraints, Quality Attributes. Prioritization of requirements, requirement combinations, feasibility of requirements. Specifics of the Availability requirement
- Utility tree: How to build and use it in design
- A template for solving architectural problems for a Solution Architect
4. Building Architecture
- Architectural styles and approaches: Monolith, microservices, SOA, serverless, client-server, hexagonal, layered, event-driven, CQRS, data pipeline, plugin, repository, cloud-based, bus-based...
- Integration architectures
- Tactics for achieving Availability, Performance, and Scalability in distributed systems
- Patterns of distributed systems
- Algorithms for building architecture for beginners and more experienced architects
5. Architectural Strategy and Roadmap
- Initiatives, projects, programs. Sponsors and stakeholders of projects and programs
- Initiative and organization change management
- The company’s technological strategy
- System development roadmap
6. Blueprints and Reference Architectures
- Differences between reference architecture and design patterns
- Typical solutions for common systems and business needs
Module 2. Solution Architect Communications
7. Organization Analysis
- Defining the structure of an organization
- Culture: Types of cultures, defining the organization’s culture. Values and behavior in different cultures
- Managing expectations
- Agreements and career
- Finding your place and path within an organization
8. Building Trust in the Architect
- Specifics and boundaries of an architect’s influence
- Demonstrating broad expertise as a way to build trust
- Communication with managers, teams, product managers, and infrastructure teams
- Should an architect have their own pet project?
9. "Selling" and Justifying Solutions
- Documentation approaches that prevent questions
- Comparison tables
- Sales techniques for presenting solutions
10. Architectural Process
- Documentation: Strategy, roadmap, HLD, LLD, ADR
- Collaborative problem-solving: Event storming, DDD, and documentation
- Tools for maintaining architecture
- The hierarchy of architects, architecture boards, governance, standards
11. Presales
- Specifics of task setting, stakeholders, and design during presales
- Template for preparing an Architecture Proposal
Module 3. The Crazy World
12. Documentation
- Formats and approaches
- Documentation and processes
- Cross-review of architectural documentation
- Reality, cases, and examples: Knowledge in one developer’s head, outdated documentation, and unused documentation
- Contracts and agreements with adjacent teams
13. Entering a Project
- Goals and expectations
- Company culture
- Stakeholders
- Reality, cases, and examples: Cursed roles, impossible tasks, failing companies, overly influential developers, incompetent architects, inflated expectations, sabotage of solutions, and team resistance
14. Architectural Process and Architecture Evolution
- Example of a small product company with 10 engineers
- Example of a small product company with 20 engineers
- Example of a successful startup with 50+ engineers
- Example of a large product company with 500+ engineers
- Example of a small outsourcing project with 10 engineers
- Example of a “medium-sized” outsourcing project with 30+ engineers
- Example of an integration project
- Example of a digital transformation project
15. Even More Reality
- New features vs. tech debt
- Approaches to working with legacy systems
- The culture of real companies
- Examples of conflicts with product teams
- Examples of conflicts with infrastructure teams
- Changing the lead architect
- Burnout during presales
16. Trends and the Architect’s Development Path
- AI prospects
- Enterprise architecture
- The architect’s development strategy
1. Architecture and the Architect
- What is architecture? Why is architecture important?
- Architectural contexts
- Types of architects, roles of a Solution Architect and an Enterprise Architect
- Methodologies: TOGAF, Zachman, FEAF. Choosing the right framework and applying it in practice
2. Business Architecture
- Value stream: How does a business create value, and why is it important for an architect?
- Business motivation: Business drivers, goals, objectives
- Stakeholder management: Identifying stakeholders, types of stakeholders, their interests. Power-Interest matrix. Practices for resolving conflicts
3. Requirements
- Functional requirements
- Non-functional requirements, assumptions. Architecture Significant Requirements, Constraints, Quality Attributes. Prioritization of requirements, requirement combinations, feasibility of requirements. Specifics of the Availability requirement
- Utility tree: How to build and use it in design
- A template for solving architectural problems for a Solution Architect
4. Building Architecture
- Architectural styles and approaches: Monolith, microservices, SOA, serverless, client-server, hexagonal, layered, event-driven, CQRS, data pipeline, plugin, repository, cloud-based, bus-based...
- Integration architectures
- Tactics for achieving Availability, Performance, and Scalability in distributed systems
- Patterns of distributed systems
- Algorithms for building architecture for beginners and more experienced architects
5. Architectural Strategy and Roadmap
- Initiatives, projects, programs. Sponsors and stakeholders of projects and programs
- Initiative and organization change management
- The company’s technological strategy
- System development roadmap
6. Blueprints and Reference Architectures
- Differences between reference architecture and design patterns
- Typical solutions for common systems and business needs
Module 2. Solution Architect Communications
7. Organization Analysis
- Defining the structure of an organization
- Culture: Types of cultures, defining the organization’s culture. Values and behavior in different cultures
- Managing expectations
- Agreements and career
- Finding your place and path within an organization
8. Building Trust in the Architect
- Specifics and boundaries of an architect’s influence
- Demonstrating broad expertise as a way to build trust
- Communication with managers, teams, product managers, and infrastructure teams
- Should an architect have their own pet project?
9. "Selling" and Justifying Solutions
- Documentation approaches that prevent questions
- Comparison tables
- Sales techniques for presenting solutions
10. Architectural Process
- Documentation: Strategy, roadmap, HLD, LLD, ADR
- Collaborative problem-solving: Event storming, DDD, and documentation
- Tools for maintaining architecture
- The hierarchy of architects, architecture boards, governance, standards
11. Presales
- Specifics of task setting, stakeholders, and design during presales
- Template for preparing an Architecture Proposal
Module 3. The Crazy World
12. Documentation
- Formats and approaches
- Documentation and processes
- Cross-review of architectural documentation
- Reality, cases, and examples: Knowledge in one developer’s head, outdated documentation, and unused documentation
- Contracts and agreements with adjacent teams
13. Entering a Project
- Goals and expectations
- Company culture
- Stakeholders
- Reality, cases, and examples: Cursed roles, impossible tasks, failing companies, overly influential developers, incompetent architects, inflated expectations, sabotage of solutions, and team resistance
14. Architectural Process and Architecture Evolution
- Example of a small product company with 10 engineers
- Example of a small product company with 20 engineers
- Example of a successful startup with 50+ engineers
- Example of a large product company with 500+ engineers
- Example of a small outsourcing project with 10 engineers
- Example of a “medium-sized” outsourcing project with 30+ engineers
- Example of an integration project
- Example of a digital transformation project
15. Even More Reality
- New features vs. tech debt
- Approaches to working with legacy systems
- The culture of real companies
- Examples of conflicts with product teams
- Examples of conflicts with infrastructure teams
- Changing the lead architect
- Burnout during presales
16. Trends and the Architect’s Development Path
- AI prospects
- Enterprise architecture
- The architect’s development strategy
Сертификат Hard&Soft Skills
]
[
Сертификат подтверждает, что
Алексей Саута
успешно окончил курс
«Solution Architect in the Wild»
продолжительностью 12 недель
Алексей Саута
успешно окончил курс
«Solution Architect in the Wild»
продолжительностью 12 недель
[
Преподаватели курса
]
Principal Solution Architect
Антон Дворников
Разработчик с 2000 года, выполнял роли разработчика, тимлида, архитектора в продуктовых компаниях.
- выстраивал архитектуру и процесс для продукта: десяток команд, 200+ инженеров, микросервисы
- в данный момент выстраивает архитектуру и процесс для системы в несколько тысяч сервисов
Разработчик с 2003 года, занимается обучением с 2008, обучением сеньоров и архитекторов с 2018. Делился экспертизой в более чем 100 митапов и конференций.
Павел стоит у основания различных сообществ IT специалистов, включая: ByChange, Free IT. Выполнял роли разработчика, тимлида, архитектора, СТО в небольших стартапах, крупных корпорациях и продуктовых компаниях:
Специализации: архитектура распределенных систем, highload, микросервисные архитектуры, системная инженерия, рост инженера, коммуникации в организации.
- Architect: Miro, EPAM
- CTO: AmadoAd Ltd., SplitMetrics, Leverice
- Tech Advisor: LeoHome Inc.
- Founder: Hard&Soft skills, ITStart, Amadoad Ltd.
Обучил более 1K разработчиков за последние 15 лет. Обучил более 200 архитекторов. Создает и проводит обучающие курсы для любых технических направлений.
Founding Teacher at Hard & Soft Skills
Павел Вейник
Пройденная программа курса
]
[
Раздел 1. Красивая теория Solution Architecture
1. Архитектура и архитектор
2. Business Architecture
3. Требования
4. Построение архитектуры
5. Архитектурная стратегия и roadmap
6. Blueprints и Reference Architectures
Раздел 2. Коммуникации Solution Architect
7. Анализ организации
8. Формирование доверия к архитектору
9. "Продажа" и обоснование решений
10. Архитектурный процесс
Раздел 3. Безумный мир
12. Документация
13. Входим в проект
14. Архитектурный процесс и эволюция архитектуры
15. Еще больше реальности
16. Тренды и направление развития архитектора
1. Архитектура и архитектор
- Что такое архитектура? Почему архитектура важна?
- Контексты архитектуры
- Виды архитекторов, роли Solution Architect, Enterprise Architect
- Методологии TOGAF, Zachman, FEAF. Выбор подходящего фреймворка, применение фреймворка на практике
2. Business Architecture
- Value stream. Как бизнес создает ценность и почему это важно для архитектора?
- Business motivation. Business drivers, goals, objectives
- Stakeholder management. Выявоение стейкхолдеров, виды стейкхолдеров, интересы стейкхолдеров. Power-Interest matrix. Практики разрешения противоречий
3. Требования
- Функциональные требования
- Нефункциональные требования, предположения. Architecture Significant Requirements, Constraints, Quality Attributes. Приоритет требований, комбинации требований, выполнимость требований. Особенности требования Availability
- Utility tree. Как строить, и как использовать при проектировании
- Шаблон решения архитектурных задач для Solution Architect
4. Построение архитектуры
- Архитектурные стили и подходы. Монолит, микросервисы, SOA, serverless, client-server, hexagonal, layered, event-driven, CQRS, data pipeline, plugin, repository, cloud-based, bus-based...
- Архитектуры интеграции
- Тактики достижения Availability, Performance, Scalability в распределенных системах
- Паттерны распределенных систем
- Алгоритм построения архитектуры для новичков и для более опытных архитекторов
5. Архитектурная стратегия и roadmap
- Инициативы, проекты, программы. Спонсоры и стейкхолдеры проектов и программ
- Инициатива и organization change management
- Технологическая стратегия компании
- Roadmap развития системы
6. Blueprints и Reference Architectures
- Отличия reference architecture от паттернов проектирования
- Типовые решения для типовых систем и запросов бизнеса
Раздел 2. Коммуникации Solution Architect
7. Анализ организации
- Определение структуры организации
- Культура. Виды культур. Определение культуры организации. Ценности и поведение в различных культурах
- Управление ожиданиями
- Договоренности и карьера
- Свое место и путь в организации
8. Формирование доверия к архитектору
- Особенности и границы влияния архитектора
- Демонстрация кругозора как способ завоевать доверие
- Коммуникации с менеджерами, с командой, с продуктом, с командой инфраструктуры
- Нужно ли делать свой pet проект архитектору?
9. "Продажа" и обоснование решений
- Способы документирование решений, который предотвращает вопросы
- Comparison tables
- Приемы продаж при презентации решения
10. Архитектурный процесс
- Документация. Strategy, roadmap, HLD, LLD, ADR
- Совместное решение задач. Event storming. DDD и документация
- Инструменты поддержания архитектуры
- Иерархия архитекторов, architecture board, governance, стандарты
- Особенности постановки, стейкхолдеров и проектирования
- Шаблон подготовки Architecture Proposal
Раздел 3. Безумный мир
12. Документация
- Форматы и подходы
- Документация и процессы
- Cross-review архитектурной документации
- Реальность, кейсы и примеры. Знания в голове одного разработчика. Устаревшая документация. Никто не пользуется документацией
- Контракты и договоренности со смежными командами
13. Входим в проект
- Цели и ожидания
- Культура компании
- Стейкхолдеры
- Реальность, кейсы и примеры. Проклятые роли. Невыполнимые задачи. Гибнущие компании. Сверхвлиятельные разработчики. Некомпетентные архитекторы. Завышенные ожидания. Саботаж решений и сопротивление команды
14. Архитектурный процесс и эволюция архитектуры
- Пример маленькой продуктовой компании, 10 инженеров
- Пример маленькой продуктовой компании, 20 инженеров
- Пример успешного стартапа, 50+ инженеров
- Пример большой продуктовой компании, 500+ инженеров
- Пример небольшого аутсорс проекта, 10 инженеров
- Пример "среднего" аутсорс проекта, 30+ инженеров
- Пример проекта по интеграции
- Пример проекта по цифровой трансформации
15. Еще больше реальности
- New features vs tech debt
- Подходы к работе с legacy
- Культура реальных компаний
- Примеры конфликта с продуктом
- Примеры конфликта с инфраструктурой
- Смена руководящего архитектора
- Выгорание на presales
16. Тренды и направление развития архитектора
- Перспективы AI
- Enterprise architecture
- Стратегия развития архитектора