Learn the benefits of strategic innovation and purposeful event-driven architecture for large-scale system design on brownfield and greenfield systems alike.
Today, businesses and software developers must rapidly innovate and compete while maintaining order and balance with software architecture. In this video, expert Vaughn Vernon teaches you to think and make decisions like a CTO and Chief Architect. Learn to identify core purpose, and then make informed decisions about architecture, programming languages, patterns, and tools to support that purpose.
You will learn about innovative thinking and how design and implementation can align with strategic business goals. You will explore how to use EventStorming, Impact Mapping, Domain-Driven Design, and Event-Driven Architecture, and to deploy "right-sized services." Whether the best choice is a monolithic architecture, microservices, or a hybrid, you will learn to identify what helps you and your team deliver what the business demands: success with strategic software.
Learn How To
Support scaling strategic innovation by identifying key architectures and design objectives
Use tools that support exploration, experimentation, and discovery-based learning
Leverage Domain-Driven Design and Event-Driven Architecture to transform "Big Ball of Mud" systems into modular monoliths, microservices, or hybrid models
Think like a Chief Architect and CTO by owning strategy and profit responsibility
About the Instructor
Vaughn Vernon is a champion of simplifying software architecture and development, with an emphasis on reactive methods. He has a unique ability to teach and lead with Domain-Driven Design using lightweight tools to unveil unimagined value. He helps organizations achieve competitive advantages using enduring tools such as architectures, patterns, and approaches, and through partnerships between business stakeholders and software developers.
Who Should Take This Course
Software developers and technically oriented managers and executives in organizations that build software for competitive advantage.
Software architect, enterprise architect, data architect, technical lead, software engineer, programmer.
Product manager, project manager, business analyst.
Chief architect, director, IT manager, VP, SVP, CxO.
Course Requirements
Basic knowledge of business software requirements, programming; software architecture and leadership is a plus but not necessary; a willingness to consider alternative approaches to software building that are driven by business strategy rather than technology fascination.

https://rapidgator.net/file/df40bfe42e65710ad4115b28f79854b8/Strategic_Monoliths_and_Microservices.part1.rar.html
https://rapidgator.net/file/84ba23d6c264704812957d7ba9b4ee72/Strategic_Monoliths_and_Microservices.part2.rar.html
https://rapidgator.net/file/5e2aa83d64415486b3e4ba739615b0f1/Strategic_Monoliths_and_Microservices.part3.rar.html