Architecture Weekly #101 - 14th November 2022
Welcome to the new week!
It’s 101st, the Dalmatians Edition! Last week I celebrated the anniversary with a Live Q&A; check the recording here. Now it’s time to move on and target the next 100.
Being an architect means that you can synthesise ideas and spot critical differences. Analytic skills and critical thinking are essential skills. A good example of that is the collaborated talk by Sam Newman and Martin Fowler discussing microservices vs monoliths:
In my last article, I tried to connect approaches that’s usually shown as a contrarian: Event-Driven and State-Based. Too often, Event-Driven is shown in its flattened version: pushing messages asynchronously through the pipe. Yet, the real power of it comes from changing the mindset and shaping our processes based on the results of the business actions we perform. It’s more logical than technical. However, it’s also something real; by making explicit business intentions, you can also get better technical efficiency, e.g. improved performance. Read more:
Understanding the concepts right can also mean money optimisation. Especially in Cloud, misuse and misunderstanding or mental cliches can cost you a lot of money. I wrote about that some time ago in How money in Cloud impacts Architectural decisions? Check a nice guidance and cost analysis between using the AWS Aurora database and the classical Postgres version on RDS:
Aligning our ideas and thinking needs to go hand in hand with our organisation. Architecture is not created in a vacuum. Check more in:
Moved already been to Mastodon? I still have that on my ToDo list. A good starting point is Marcin’s article:
Last but not least, listen to David Whitney’s thoughts about Open Source. I fully sign with all the critical thoughts and ideas he shared in the .NET Rocks episode. The OSS model is broken, and it has to change. If you’re not contributing and thinking that those are just dramas, then you should reevaluate that, as the current status may hit you soon.
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!
Architecture Weekly is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.