It was a fun and easy way to learn difficult content.
It's much better than some books that are difficult to read.
I'm really looking forward to the next practical part.
Thank you, instructor.!!
5.0
Minkyu Ha
100% enrolled
It seems to be a good guide for extracting domain models through event storming.
I spent a lot of time reading books related to DDD because of the ambiguity of the terms themselves,
but this lecture was a good guide.
I am looking forward to the next lecture since it says that the content related to direct implementation will be covered.
Actually, I expected more about implementation, and the recording quality is not that clear,
but the lecture itself was very helpful to me.
5.0
kailis
100% enrolled
These were familiar words, but the complex concepts in my head have become concrete!
What you will gain after the course
Domain-Driven Design (DDD)
Hexagonal architecture
Strategic Design
Tactical Design
Event Storming
Layered architecture
Domain Modeling
API Design
MSA
If you want to learn the core of DDD for sure!
Microservices design More flexible, more powerful.
Oh, are you talking about me?
😥
I understand the general concept of MSA , but I have no idea how to actually split it into microservices and design it, and it's just difficult.
🙄
Don't microservices just need to have a public REST API? What other design is needed?
😵
Asynchronous event communication seems to be used a lot... What kind of business cases are they used for? How do you design and distinguish between synchronous and asynchronous communication?
What is important in order to independently deploy and change microservices in an MSA structure? It is to identify microservices that are functionally cohesive and have few dependencies on other services . In addition, the internal structure of microservices must be flexible to technological changes, allowing for agile response to business changes.
For this purpose, domain-driven design (DDD) techniques are mainly used for microservice design, and hexagonal architecture is mainly used for internal architecture. In this lecture, we will explain how to design microservices with a cohesive and flexible structure based on domain-driven design and hexagonal architecture.
2 Hottest Techniques in Microservices Design 🌳
Domain Driven Design (Domain-Driven Design, DDD)
A development methodology that builds software architecture around business strategy and domain patterns.
Hexagonal architecture (Hexagonal Architecture)
An architectural pattern that manages the flow of dependencies from domain-centric sources to outside sources.
Only for this lecture Check out the features 📗
The lecture is given in a raw voice, based on the experience of practitioners. 😁
We aim for the ideal of microservices, but present an approach that reflects reality.
This course consists of concepts and hands-on practice using online tools.
We introduce hot field standards and judgment(?) techniques used in actual microservice design .
So, this is helpful for these people! 🏃♀️
In microservice design I want to use event storming Technology/Design Leader
Microservice design criteria and Thinking about how to Microservice Developer
Domain Driven Design (DDD) and Interested in implementing Backend Developer
Starting with theory Learn through practice Microservices Design 💻
Understanding the concept of domain driven design
Domain-Driven Design - Learn about several concepts of strategic design: domain models, subdomains, ubiquitous language, and bounded contexts.
The most practical microservice derivation technique: Event Storming
We will explain the Event Storming Workshop, the easiest and simplest microservice derivation technique.
Introduction to various microservice business logic implementation patterns
We'll explore several patterns for designing business logic inside microservices (transaction scripts, active records, domain models, etc.) and what choices to make.
Understand various internal architecture patterns for defining the internal structure of microservices.
Let's think about the desirable internal structure of microservices through comparison with the limitations of the traditional layered architecture and the features of the hexagonal and clean architectures.
Event Storming Workshop Practice
We will conduct an event storming workshop using the online tool Miro on the topic of book lending system.
Practice creating context mapping diagrams
Define relationships in the bounded context identified through event storming and define candidate microservices.
Domain Modeling Practice
Let's design the heart domain model of a microservice using the tactical design tools of domain-driven design.
So, you can do something like this! 😎
You will understand the concepts of strategic design/tactical design of domain-driven design and learn how to utilize them in microservice design.
Event storming can be used to analyze work and derive microservices.
You can define criteria for the business logic implementation patterns and internal architectural styles of individual microservices.
Domain-driven design - You can design the domain model within your microservices by applying tactical design techniques.
In this lecture Knowledge sharer is 💁♂️
23-year developer, han jeong heon
Current SI software engineer at a large corporation
Leading development methodology and design method for multiple large-scale next-generation projects
Lectures on SW courses at Myongji University and Seoul National University of Science and Technology, Korea Information Technology Research Institute (KITRI), and LG Electronics MSA course
Multicampus, Korea Standards Association, Korea Quality Association MSA Course Mentoring
Areas of expertise: Development methodology, software architecture/design/development techniques
Wikibooks “Microservice Development Starting with Domain-Driven Design” (2022)
National Institute for Lifelong Education K-MOOC “Microservice Design and Implementation” Course
Development of “Microservice Design and Implementation” course
“Microservice Development Starting with Domain-Driven Design” published
Q&A 💬
Q. Do you cover both theory and practice in class?
The first half of this course covers theory, and the second half covers practice. It is designed to help you understand the general concepts and then understand how the techniques are used through practice.
Q. Can job seekers without work experience or non-majors also take the course?
Even if you don't have cloud experience, it's an approachable level for developers with actual legacy experience. However, if you don't have practical experience, you may have difficulty with terminology, etc. However, even if you're not a major, if you have experience completing a boot camp, you should be able to take the course without difficulty.
Q. What level of content is covered in the class?
This lecture will cover the overall theory of microservices for domain-driven design, derive microservices through real-world business examples, and design their internals. Implementation is being prepared as a separate course.
Current domestic SI company software engineer (SA, AA)
Led development methodologies and design methods for numerous large-scale next-generation projects
Lectured on Cloud and SW subjects at Myongji University and Seoul National University of Science and Technology
Lectured on MSA courses at SK C&C, Korea Information Technology Research Institute (KITRI), and LG Electronics
Mentoring for MSA courses at Multicampus, Korean Standards Association, and Korea Management Association; mentoring for the web development course at Spharos Academy.
Areas of Expertise: Development Methodologies, Software Architecture/Design/Development Techniques
2022, Wikibooks "Microservices Development Starting with Domain-Driven Design", Author
Developed and lectured the "Microservice Design and Implementation" course for K-MOOC, National Institute for Lifelong Education.
It was a fun and easy way to learn difficult content.
It's much better than some books that are difficult to read.
I'm really looking forward to the next practical part.
Thank you, instructor.!!
It seems to be a good guide for extracting domain models through event storming.
I spent a lot of time reading books related to DDD because of the ambiguity of the terms themselves,
but this lecture was a good guide.
I am looking forward to the next lecture since it says that the content related to direct implementation will be covered.
Actually, I expected more about implementation, and the recording quality is not that clear,
but the lecture itself was very helpful to me.