Whole Architecture Weekly content is free now!

Hi, the only constant in the world is change. Seven months ago, I made a big change and made the Architecture Weekly a paid newsletter. Now, I have decided to make it fully free.

What’s more, I made all past content available for free! You can read all past articles now:

• Mastering Database Connection Pooling

• Queuing, Backpressure, Single Writer and other useful patterns for managing concurrency

• Is It Production Ready?

• Talk is cheap, show me the numbers! Benchmarking and beyond!

• Using S3 but not the way you expected. S3 as strongly consistent event store

• Show me the money! Practically navigating the Cloud Costs Complexity

• When Logs and metrics are not enough: Discovering Modern Observability

• Making your system observability predictable

• Why to measure and make our system observable? How to reason on chaotic world

• Don't Oversell Ideas: Trunk-Based Development Edition

• Tech Debt doesn't exist, but trade-offs do

• Building your own Ledger Database

• Ordering, Grouping and Consistency in Messaging systems

• Deduplication in Distributed Systems: Myths, Realities, and Practical Solutions

• The Write-Ahead Log: The underrated Reliability Foundation for Databases and Distributed systems

• On getting the meaningful discussions, and why that's important

• Distributed Locking: A Practical Guide

• Locks, Queues and business workflows processing

• Thoughts on Platforms, Core Teams, DORA Report and all that jazz

• How Kafka Producer Works internally

• Kafka Consumers: Under the Hood of Message Processing

• Understanding Kafka's Consumer Protocol: A Deep Dive into How Consumers Talk to Brokers

• Defining Your Paranoia Level: Navigating Change Without the Overkill

• How does Kafka know what was the last message it processed? Deep dive into Offset Tracking

• So you want to break down monolith? Read that first.

And watch all past webinars:

• #1 - From CRUD to Event Sourcing

• #2 - Keep your streams short! Or how to model Event-Sourced systems efficiently

• #3 - Implementing Distributed Processes

• #4 - From CRUD to CQRS in Practice

• #5 - Architecture Weekly 100 Edition - Live Q&A

• #6 - Alexey Zimarev - You don't need an Event Sourcing framework. Or do you?

• #7 - Design and test Event-Driven projections and read models

• #8 - Slim down your aggregates!

• #9 - Radek Maziarka - Modularization with Event Storming Process Level

• #10 - PostgreSQL Superpowers in Practice

• #11 - Maciej "MJ" Jędrzejewski - Evolutionary Architecture: The What. The Why. The How.

• #12 - Jeremy D. Miller: Simplify your architecture with Wolverine

• #13 - Yves Goeleven - The Fantastic 9

• #14 - Mateusz Jendza - Why Verified Credentials is the Future of Digital Identity!

• #15 - Mário Bittencourt: Leveraging BPMN for Seamless Team Collaboration in Software Development

• #16 - Papers We Love #1 - Sagas (Hector Garcia-Molina, Kenneth Salem)

• #17 - Simple patterns for events schema versioning

• #18 - Andrea Magnorsky: Introducing Bytesize Architecture Sessions!

• #19 - Laïla Bougriâ: Debug your thinking

• #20 - Papers We Love #2 - How do committees invent? (Melvin E. Conway)

• #21 - Michael Drogalis: Building the product on your own terms

• #22 - On Performance Testing with Jarosław Pałka

• #23 - Gojko Adzic on designing product development experiments with Lizard Optimization

• #24 - Frontent Architecture, Backend Architecture or just Architecture? With Tomasz Ducin

• #25 - Applying Observability: From Strategy to Practice with Hazel Weakly

• #26 - React Query: A solution for Frontend State Management challenges? With Tomasz Ducin

• #27 - Documenting Event-Driven Architecture with EventCatalog and David Boyne

• #28 - Practical Introduction to Event Sourcing with Emmett

I also made them available on my YouTube Channel: https://www.youtube.com/@event-driven. So click subscribe, bell and all that stuff!

I believe that all of that gives you more content than a lot of books or paid online courses.

Why did I do it? Am I mad? What’s the catch?

In past years, I delivered many unique materials. I also increased the number of subscribers, both paid and regular ones. Preparing the type of content that I try to deliver each week quality content, takes time and focus.

I still want to do that and produce new articles, but I decrease the pressure to do full-length and deep dives each week—sometimes even on weekends. And I’m not sure how about you, but I prefer to spend weekends with my family.

The number of paid subscribers grew, but still insufficient to fully focus on Architecture Weekly. That’s fine, as I have other work, such as consultancy and training, open source work, and contracts.

I believe that making the Architecture Weekly free newsletter should free some time for me, reduce the pressure I put on myself and let me focus on other stuff.

I still plan to deliver similar content as I did, keeping the weekly cadence, maybe in a slightly different form, or changing it to every other week later on. We’ll see.

So if you worry, don’t. I don’t plan to shut it down, but do it more for fun than profit. Quality should still be here, but maybe a bit lightweight form.

I would appreciate it if you shared the news with your friends, so they could also benefit from those free materials. I believe they’re worth it.

What are your thoughts?

Cheers!

Oskar