Architecture Weekly #132 - 19th June 2023
Welcome to the new week!
Do you know that we already had 10 webinars and over 16 hours of learning materials for paid subscribers community? No? Then check more details here. Next week, we’ll have the next one!
This time we’ll have a special guest: Maciej "MJ" Jędrzejewski.
He’ll talk about Evolutionary Architecture: The What. The Why. The How.
Here are the details from himself:
Are you overwhelmed by the complexity of modern software architectures?
Not sure whether to start with microservices or a monolith? Are you worried about ending up with an overly complicated architecture or a big ball of mud?
In "Evolutionary Architecture: The What. The Why. The How." I will present a practical, evolutionary approach to software architecture that is designed to grow and adapt with your application.
Whether you are a beginner or an experienced folk, this talk will give you the insights you need to build architecture that is flexible and manageable over time.
Maciej is a software architect and facilitator of modern software development practices that allow shortening the feedback loop in every area of a lifecycle, e.g. short-living branches, vertical slices, canary releases, continuous delivery, continuous deployment, and more. His main areas of interest - Domain-Driven Design and Artificial Intelligence.
Check more on his blog and youtube channel. I’m personally super happy that he’ll be presenting on this topic, as I love his pragmatic approach based on his strong experience with real projects. Plus, Maciej is also a member of our community, which makes me happy that we’re getting more content not from me but from our members. You can join it too, and discuss with us more on Discord!
Speaking about the community, I wrote a promised recap of the Event Sourcing Live conference. If you’d like to see what the hot topics were discussed there, read more in:
Videos are not yet available, but I’ll keep you posted when they’re out.
Still, you can watch videos on Event-Driven Architecture from Kafka Summit and EDA Summit on demand:
The developer community also provided feedback on the annual StackOverflow survey. Read more on what’s hot and what’s not. TLDR, JavaScript is still doing well.
Would you like to read a dedicated article from me analysing the results?
An interesting message from the AI trendsetters was published.
That includes chiefs of OpenAI, Google DeepMind, Bill Gates, university professors etc. I can spare you from clicking; this is the entire message:
Mitigating the risk of extinction from AI should be a global priority alongside other societal-scale risks such as pandemics and nuclear war.
For me, it looks like due diligence. Something like saying, “I’m not sexist, but…”. So they could say, “We were telling you, that it may end up like that, but no one stopped us”. I hope I’m cynical, but I’m afraid some of those signatories are more cynical than me.
Humanloop published an article due to talking to people from OpenAI. OpenAI shared their plans, but they probably decided they shared too much. Humanloop had to remove it, but hey, on the Internet, nothing is vanishing:
Some people are saying that AI will fire us; Jan Kammerath wrote that Kubernetes and Kafka will get you fired:
I do not fully agree with this article; it’s a bit too rantish, but I agree with the message that we went too far with those tooling. It’s not an issue with those tools per se, but with us looking for the Holy Grail. Those solutions are great for people with the skills, justification for additional costs, or legal needs. Still, there are simpler ways to iterate if we’re building a small system.
That’s why we need a pragmatic approach, understanding the architecture patterns, their strong parts and their limitations. We need to see if they match our context. We should check for technical matching and the budget and people we have. Check more about that in:
Matthew Foster - Linking Modular Architecture to Development Teams
William Brander - Top 5 techniques for building the worst microservice system ever
A good way to learn how to do that is by practising Architecture Katas:
Jeremy Miller just released Wolverine 1.0. That means it’s production-ready. If you’re in the .NET space and doing Messaging/CQRS/EventDriven approach, then that’s something that you should at least investigate. It can cut you a lot of boilerplate work and headaches around resiliency, fault tolerance, and multi-tenancy. It’s also playing well with Marten.
Last but not least, check the video below. I laughed a lot about it:
Check also other links!
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 the Ukraine humanitarian organisation, Ambulances for Ukraine or Red Cross.
Architecture
Matthew Foster - Linking Modular Architecture to Development Teams
William Brander - Top 5 techniques for building the worst microservice system ever
DevOps
Databases
AI
AWS
Azure
Java
JavaScript
The Cloudflare - A Community Group for Web-interoperable JavaScript runtimes
Code with Hugo - Mocking/stubbing the current Date in Jest tests
Josh Goldberg - Configuring ESLint, Prettier, and TypeScript Together
.NET
Chris Klug - Introduction to Actor-based Development with Project Orleans
Stefan Pölz - Let's Code an incremental source generator with Roslyn
Coding Life
Management
Harvard Business Review - Remote Work Should Be (Mostly) Asynchronous
Dan North - Why Agile Doesn't Scale & What You Can Do About It