Are you kicking off a new project or transitioning from a monolith architecture to microservices? An uninformed design choice for your system can introduce costly bottlenecks. In this hands-on workshop, Kacper Gunia will share how to design a system that takes into account your business's social and technical structures.
This course has been developed by Kacper Gunia, international speaker and expert specialising in bridging the gap between IT and Business.
In theory, by making services smaller we should be able to improve these metrics and benefit from a new architecture. Unfortunately, this approach is missing an important point. If we want to have truly autonomous teams and services that are not tightly coupled with each other, first we need to understand the domain. Only then we will be able to design a loosely coupled architecture that enables the fast flow of change.
In this course, you will start exploring and understanding your problem space - the domain. With this knowledge, you will be able to iteratively design a loosely coupled system aligned with business needs and organisational structure and bridging the gap between IT and the Business. In order to achieve these goals, Kacper will navigate the class through the use of a number of tools and techniques bringing his wealth of experience into hands-on practice and application.
Learn how to:
- Analyse and understand the business model using Business Model Canvas
- Gain a common understanding of a business domain using Event Storming
- Choose service boundaries using modelling heuristics
- Validate design with core use cases and identify coupling in a system
- Classify contexts and prioritise areas for strategic investment
- Organise teams aligned with the business, domain and cognitive load
Domain Discovery and Strategic Design
- Learn how to collaboratively model and understand the business
- Functional thinking
- Learn to understand how technology contributes to business goals
- Learn how to model context boundaries
- Learn how to design autonomous teams aligned with the software and domain
- Learn why sociotechnical architectures constantly evolve
- Learn how to evolve sociotechnical architectures for business, technical, and social reasons
Technical manager and business stakeholders kicking off a new project or transitioning from a monolith architecture who are keen to improve team autonomy, reduce lead time and maximise strategic investment.
To make the most of this course, you need to have 3-5 years minimum experience working with software development or technical teams.