0:00 All right, so before we go ahead and get started with building out our 0:03 application, 0:04 I wanna go ahead and dive a bit into some theory and 0:07 architecture around the principles that are gonna drive what we're 0:11 actually building in this course, and why we're actually building it in a 0:15 certain way. 0:17 Now, there's a few terms that you're gonna hear me talk about quite 0:20 a bit in this 0:21 course, such as clean architecture, hexagonal 0:25 architecture, and domain-driven design. 0:29 So let's go ahead and break down each of these concepts 0:32 briefly and 0:33 understand why we're actually applying them and the benefits that they are going 0:37 to provide us. Now, what we have here is a common 0:40 diagram that outlines a typical clean 0:44 architecture, 0:45 and what it comprises of is three major 0:49 layers. You can think of these as separate layers 0:52 of our architecture. 0:53 At the core of our application, in the innermost part of the 0:57 application architecture, is the domain. 1:00 This domain piece is where the actual core business 1:03 logic of our application lives. Now, you might be wondering, what 1:07 is business logic in this context? 1:10 What are we actually talking about? 1:12 Business logic is essentially the rules of our application. 1:16 So when we actually send requests to our back end in this course, we're 1:20 gonna be placing orders, payments, and creating 1:24 products. However, we're gonna have business logic in the 1:27 application. There's gonna be actual rules in our 1:30 application where 1:31 we have to decide, what does it mean when an order is 1:34 successful? How do we actually calculate an order 1:37 total and 1:38 apply discounts? So sort of these business rules that 1:42 drive the actual application itself. 1:45 Now, an important part about this domain 1:48 is it's 1:49 agnostic to the actual back-end technology 1:53 that it's living in, right? These back-end rules a product person
The rest of the transcript is for members.
Sign in 