This pattern is crazy, or I'm an idiot - Learning Domain-Driven Design by Vlad K [41:34-42:57]

Central to the way that the business functions. And then all sort of external functionality gets abstracted away. Yes. And again, I think that anyone who like if you've used dependency injection in a serious way, you do this naturally, right? This is, this is this idea that maybe I have some bootstrap step or a knit step. And I will have my log provider or I'll have my telemetry provider or have my database provider that kind of comes in. And a business logic has no idea that like what it's doing other than maybe I've given it the ability to, you know, initialize client in that client, it just happens to be the DB client. It maybe has the ability to do, you know, some calls and do some stuff. But what DB? It has no idea. Right. Right. I'm not hard coding, you know, maybe Aurora Postgres, you know, implementation details into my application. It's completely abstracted away. My adapter handles the idiosyncrasies of whatever flavor of Postgres I'm using or what I mean, maybe maybe I'm using SQLite for local dev and then Postgres and production. My business application, I mean, the application doesn't know the difference. It just knows that my little adapter that I'm using should, you know, be in a certain shape. Yeah, I really like,