Architecture Weekly #99 - 31st October 2022
Architecture Weekly #99 - 31st October 2022
Welcome to the new week!
You need to celebrate small successes; when I started Architecture Weekly almost two years ago, I didn’t think it would last so long. It started as a way to organise my neverending open tabs in Firefox. The next week will be 100 editions; let’s have some fun then!
I decided to do a Live Q&A on my Youtube Channel. It will happen Monday 7th of November at 4 PM CEST. Click the ring bell, etc., to not forget about it:
Please also send me your questions; you can ask me anything! I’ll try to answer all questions live, join it, and ask questions during the live stream!
Here’s the Google Form link: https://forms.gle/RgB51b7aWMNqekfk8.
Last week was pretty busy for me; I did a talk at my hometown Java User Group explaining how Event Sourcing can help in not losing business data. I also spoke for the first time at the PHP conference. Don’t worry, I didn’t try to cheat that I know it well, but I talked about the common issues: Facts and Myths about CQRS.
In the same way, James Hickey wrote a great, thorough explanation of the myths about Eventual Consistency in Event Sourcing. Read it not only if you use Event Sourcing; most of that also applies to the event-driven approach in general.
The messaging guarantees are foundational when we think about our architecture. As you know, I’m a massive fan of the Outbox Pattern. It’s great, Postgres is great, but they can create a surprisingly head-aching mixture. I wrote about that in my last article:
David Heinemeier Hansson is a controversial guy. He and his company often go in the opposite direction to the trends. Now they are challenged if the Cloud is always the best solution. Want to know why they just got back to bare metal? Check more:
Don’t also miss the latest Thoughtworks technology radar. You need to be careful and don’t take all of that for granted, but it’s always a good source of knowing what’s trending and obsolete. Especially for the obsolete parts, this report is rarely wrong (for the new stuff, it may not always catch up quickly).
Yves Goeleven shared his Software Delivery Process. You don’t always see experienced architects taking their time to share their toolset:
Check, also other links and don’t forget to join my workshop with Practical Introduction to Event Sourcing!
Cheers
Oskar
p.s. I invite you to join the paid version of Architecture Weekly. It already contains the exclusive Discord channel for subscribers (and my GitHub sponsors), monthly webinars, etc. It is a vibrant space for knowledge sharing. Don’t wait to be a part of it!
p.s.2. Ukraine is still under brutal Russian invasion. A lot of Ukrainian people are hurt, without shelter and need help. You can help in various ways, for instance, directly helping refugees, spreading awareness, and putting pressure on your local government or companies. You can also support Ukraine by donating, e.g. to Red Cross, the Ukraine humanitarian organisation. You may also consider joining Tech for Ukraine initiative.
Architecture
James Hickey - Event Sourcing: Without Eventual Consistency?
Russell Ackoff - Why Few Organizations Adopt Systems Thinking
Emmanuel Bernard, Clement Escoffier - Kafka: a map of traps for the enlightened dev and op
Databases
AWS
Azure
Functional Programming
Java
Kotlin
.NET
David Wengier - What's new in C# 11 now with less controversy!!
Patrick Smacchia - Managed pointers, Span, ref struct, C#11 ref fields and the scoped keyword
James Randall - CSharp port of Wolfenstein using the funky new language features
Jeremy D. Miller - Using Context/Specification to better express complicated tests