Basic Things
After working on the initial stages of several largish projects, I accumulated a list of things that share the following three properties:
On over-engineering; finding the right balance
A big debate among developers is whether to write code for today’s problem or to build a general-purpose solution for future needs. Both approaches have their pros and cons. Specific-purpose code can quickly become messy. But overly general code can add unnecessary complexity. This post, obviously opinionated, argues for a middle ground. That’s the sweet spot, as always.
تو این ویدیو اول سراغ تاریخچه معماری رفتیم و بعد به این رسیدیم که چرا توی یه جنگلی از اسامی معمارگونه گیر کرده ایم و سعی داریم از این همه اسامی و الگوها و معماریهای مختلف رو طبقه بندی کنیم.
02:30 History of the Software Architecture
16:00 Architecture vs Design
19:00 Software Architecture vs Software Design
Vertical Slice Architecture, not Layers!
Why Vertical Slice Architecture? Nobody wants to deal with a system that is hard to change and easy to introduce bugs because it's a spaghetti code mess of various technical concerns. Clean Architecture is popular because it separates concerns into many different layers. But why are we organizing code by layers? Does adding a new feature require you to modify files across multiple projects in your UI, business, and data access layers? Vertical Slice Architecture is about how you organize code and focus on features instead of technical layers will make your system easier to change.
Most traditional .NET applications are deployed as single units corresponding to an executable or a single web application running within a single IIS appdomain. This approach is the simplest deployment model and serves many internal and smaller public applications very well. However, even given this single unit of deployment, most non-trivial business applications benefit from some logical separation into several layers.
