Architecture Patterns with Python

Wow this book is a goldmine for architecture patterns. I love how easy it is to get into a topic and quickly grasp it.<p>Having said that, from a practical and experience standpoint, using some of these patterns can really spiral out into an increased complexity and performance issues in Python, specially when you use already opinionated frameworks like Django which already uses the ActiveRecord pattern.<p>I’ve been in companies big and small using Python, both using and ignoring architectural patterns. Turns out all the big ones with strict architectural (n=3) pattern usage, although “clean”, the code is waaaay to complex and unnecessarily slow in tasks that at first glance should had been simple.<p>Whereas the big companies that didn’t care for these although the code was REALLY ugly in some places (huge if-else files&#x2F;functions, huge Django models with all business logic implemented in them), I was most productive because although the code was ugly I could read it, understand it, and modify the 1000 lines of if-else statements.<p>Maybe this says something about me more than the code but I hate to admit I was more productive in the non clean code companies. And don’t get me started on the huge amount of discussions they avoided on what’s clean or not.

Some parts of this book are extremely useful, especially when it&#x27;s talking about concepts that are more general than Python or any other specific language -- such as event-driven architecture, commands, CQRS etc.<p>That being said, I have a number issues with other parts of it, and I have seen how dangerous it can be when inexperienced developers take it as a gospel and try to implement everything at once (which is a common problem with any collection of design patterns like this.<p>For example, repository is a helpful pattern in general; but in many cases, including the examples in the book itself, it is a huge overkill that adds complexity with very little benefit. Even more so as they&#x27;re using SQLAlchemy, which is a &quot;repository&quot; in its own right (or, more precisely, a relational database abstraction layer with an ORM added on top).<p>Similarly, service layers and unit of work are useful when you have complex applications that cover multiple complex use cases; but in a system consisting of small services with narrow responsibilities they quickly become overly bloated using this pattern. And don&#x27;t even get me started with dependency injection in Python.<p>The essential thing about design patterns is that they&#x27;re tools like any other, and the developers should understand when to use them, and even more importantly when <i>not</i> to use them. This book has some advice in that direction, but in my opinion it should be more prominent and placed upfront rather at the end of each chapter.

I’m a Typescript dev but this book is one of my favorite architecture books, I reference it all the time. My favorite pattern is the fake unit of work&#x2F;service patterns for testing, I use this religiously in all my projects for faking (not mocking!!) third party services. It also helped me with dilemmas around naming, eg it recommends naming events in a very domain specific way rather than infrastructure or pattern specific way (eg CART_ITEM_BECAME_UNAVAILABLE is better than USER_NOTIFICATION). Some of these things are obvious but tedious to explain to teammates, so the fact that cosmic python is fully online makes it really easy to link to. Overall, a fantastic and formative resource for me!

I see Python at a nice glue language.<p>I grew tired from the forced OOP mindset, where you have to enforce encapsulation and inheritance on everything, where you only have private fields which are set through methods.<p>I grew tired of SOLID, clean coding, clean architecture, GoF patterns and Uncle Bob.<p>I grew tired of the Kingdom of Nouns and of FizzBuzz Enterprise Editions.<p>I now follow imperative or functional flows with least OOP as possible.<p>In the rare cases I use Python (not because I don&#x27;t want to, but because I mainly use .NET at work) I want the experience to be free of objects and patterns.<p>I am not trying to say that this book doesn&#x27;t have a value. It does. It&#x27;s useful to learn some patterns. But don&#x27;t try to fit everything in real life programming. Don&#x27;t make everything about patterns, objects and SOLID.

Hmm let&#x27;s see we&#x27;re going to<p>- Reimplement SQLAlchemy models (we&#x27;ll call it a &quot;repository&quot;)<p>- Reimplement SQLAlchemy sessions (&quot;unit of work&quot;)<p>- Add a &quot;service layer&quot; that doesn&#x27;t even use the models -- we unroll all the model attributes into separate function parameters because that&#x27;s less coupled somehow<p>- Scatter everything across a message bus to remove any hope of debugging it<p>- AND THIS IS JUST FOR WRITES!<p>- For reads, we have a separate fucking denormalized table that we query using raw SQL. (Seriously, see Chapter 12)<p>Hey, let&#x27;s see how much traffic MADE.com serves. 500k total visits from desktop + mobile last month works out to... 12 views per MINUTE.<p>Gee, I wish my job was cushy enough that I could spend all day writing about &quot;DDD&quot; with my thumb up my ass.

I started writing python professionally a few years ago. Coming from Kotlin and TypeScript, I found the language approachable but I was struggling to build things in an idiomatic fashion that achieved the loose coupling and testability that I was used to. I bought this book after a colleague recommended it and read it cover to cover. It really helped me get my head around ways to manage complexity in non trivial Python codebases. I don’t follow every pattern it recommends, but it opened my eyes to what’s possible and how to apply my experience in other paradigms to Python without it becoming “Java guy does Python”.<p>I cannot recommend it enough. Worth every penny.

Truly one of the great python programming books. The one thing that I found missing was the lack of static typing in the code, but that was a deliberate decision by the authors.

I have this on my shelf. It&#x27;s a small volume, similar to K&amp;R, and like that book mine is showing visible signs of wear as I&#x27;ve thumbed through it a <i>lot</i>.

This was a great read and summary! About three years ago, I worked in a C#&#x2F;.NET DDD environment, and now revisiting these concepts in Python really distills the essential parts. As I said, great read — highly recommend it if you&#x27;re also into this kind of stuff.

Oh neat, I read the paper back of this book maybe two and a half or three years or so ago. I enjoyed it quite a bit. They do a good job at keeping tests a first class topic and consistently updating them with each addition. Some older architecture books don&#x27;t treat testing as being as high up in their priorities. I&#x27;ve just found that having tests ready, easy to write, and easy to update, makes the development process more enjoyable for me since it&#x27;s less manual for running the code to check for issue - tighter feedback look I guess.<p>I will say that some of the event oriented parts of this book were very interesting, but didn&#x27;t seem as practical to implement in my current work.

Even though most people might think of web architectures when it comes to this book, we used this to design an architecture for an AI that optimises energy efficiency in a manufacturing factory.<p>Great book!

I would have expected the book mentioning something about the concept of DTOs at some point. What could be the reason it doesn&#x27;t?

I don’t understand the need for most of the patterns described in this book. Why abstract away SQLalchemy using a Repository when it is already an abstraction over the database? What’s the purpose of the unit of work? To me hand rolling SQL is much more maintainable than this abstraction soup

Excellent sequel to the goat book (TDD with Python), that got me to deploy my first real web application.

No mentioning of of <a href="https:&#x2F;&#x2F;polylith.gitbook.io&#x2F;polylith" rel="nofollow">https:&#x2F;&#x2F;polylith.gitbook.io&#x2F;polylith</a>? Is it related at all?

Great source for understanding how DDD works in a larger context. I love how concrete it is

“ If you’re reading this book, we probably don’t need to convince you that Python is great”<p>I actually do. It’s slow, buggy and not type safe.<p>Everything good about Python is actually C, namely the good packages. They’re not written in Python, because Python is shit.

Great stuff, thank you for sharing

Unfortunately <a href="https:&#x2F;&#x2F;www.cosmicpython.com&#x2F;book&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cosmicpython.com&#x2F;book&#x2F;</a> does give a 404 - this is a very bad architectural choice for web applications. I hope their other tips are better.