Architecture Weekly #121 - 3rd April 2023
Welcome to the new week!
Last Thursday, we did the next webinar for the community of Architecture Weekly paid subscribers. We asked ChatGPT to provide us with an example of an aggregate. It did not disappoint us and provided a code with many things to slim down, so we did!
Watch the webinar to see how effectively design aggregates focused on business logic!
Speaking about ChatGPT, as you might know, I've spent a lot of time with it in the last two weeks. I decided to share my findings on whether it's a revolution and whether we should be scared of it.
That's not yet another ChatGPT hype/criticism piece of work. I've tried to explain the foundations of how it works, where it's useful and where it's not backing it up with reference links. All of that is based on my personal experience and my conclusions. Read more:
It’s good to catch up with the latest news about AI, but let’s now cache up with other stuff. Yeah, I’m not the best in-jokes, but at least I’m quite good at finding decent links. So check a great explanation on how Netlifx uses/used cache in their services and how foundational it is for their architecture:
See also how nowadays, using CloudFlare can skyrocket your cache management and submarine your bills.
That may or may not be your best decision. If you’re solving some issue with cache, you’re usually ending up with two issues instead. Still, whatever you decide, log it. Never enough good resources around Architecture Decision Records. Read more in:
I’m not sure if Google logged it, but they decided to allow you to use their AlloyDB locally on your notebook and in your project. What’s AlloyDB? It’s yet another Postgres-based database engine enabling your application to scale up on the cloud. Read more:
Speaking about the local environment. I remember days when all was installed on the box. After a few months, the computer was so sluggish that it had to be reinstalled. Now we could do better than that. Check a free online course on how DevContainers can help you in setting up such one:
Seeing the new inventions in Frontend land, I must check which year. It’d be great if Frontend and Backend world talked with each other more often. Then maybe we could achieve fewer cycles and reinvent one side of what others knew a few years ago. See:
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
Scott Mansfield - Caching at Netflix: The Hidden Microservice
Troy Hunt - To Infinity and Beyond, with Cloudflare Cache Reserve
Grygoriy Gonchar - A Simple Framework for Architectural Decisions
Microsoft - Microsoft Teams: Advantages of the new architecture
Charity Majors - Architects, Anti-Patterns, and Organizational Fuckery
Databases
DevOps
Testing
API
Frontend
AI
ZeroHedge - Italy Bans OpenAI's ChatGPT Over Privacy Concerns
TechCrunch - Microsoft lays off an ethical AI team as it doubles down on OpenAI
AWS
.NET
Adam Furmanek - Implementing async with coroutines and fibers - project Loom in C#
Conner Phillis - Sequential GUIDs in Entity Framework Core Might Not Be Sequential