Lesson 190 - Logical vs Physical Architecture

In Lesson 177 I talked about logical architecture components and how they relate to the structure of the source code within a system. In this lesson I take a higher-level approach, describing how a logical architecture differs from a physical architecture, and why a logical architecture is important.

[Liamshin_Ilia]

Thank you for the lesson, Mr.Richards 👍

[sinamobasheri]

I'm really grateful for these lessons sir thank you ✨️

[alexsharma]

Good one Mark.
One question - generally we are designing these kinds of diagram in the initial phase of project. At that time normally codebase is still under development.

How can we map project folder structure with logical diagram when codebase is not ready?

[Grushkovy]

Is there some intermediate type of architecture? When designing systems (usually based on some acceptance criteria, business designs etc.) my teams often were creating something similar to this logical architectures but with some extra details, like: "here we want to write data do DB", "here we want to send data to other component" but without specifying if that DB is Postgres, Cassandra, Mongo or whatever else or without specifying if data will be sent over HTTP, TCP, kafka etc. I feel like both architectures on their own are a bit lacking, and leave too many unanswered questions and connecting them like you shown at the end of video may result with very complicated diagrams where average engineer may be quickly lost.

[mahdi]

Excellent video, thank you. I learn a lot from your books AND your videos.

Can you please provide some tips on how to connect logical and physical architecture together, effectively and clearly? The way you pinpointed (8:52) can easily get convoluted, messy and inconceivable as the number of compoents increase.

Also, how different deployment models are shown / expressed in logical architecture?