Architecture Weekly #153 - 13th November 2023
Welcome to the new week! Are you scared about GDPR? Or maybe annoyed? Do you think that's about user data removal? I have something for you. In the latest article, I went through the common challenges and those that may surprise you and as always provided some guidance on what to do with them. I think that’s a decent guide explaining how to deal with common mishaps. My take on GDPR and related regulations is that they're needed. In IT, we didn't care much about what data we store, how long and what we're doing with them. As we didn't care about the proper Data Governance practices, someone had to force them on us. Just check those links:
You also had numerous examples in the previous editions. Regulations don't need to be scary as long as we’re not building our financial model based on our users’ privacy. I think that if we're applying sane data management practices and do it as the default choice, then as a result, we'll get a system that's more maintainable and manageable. And removing user data won't be a big issue. Speaking about regulations, read a decent explanation from Mark Nottingham of the web regulators’ responsibilities (like W3C) and how we should think about them as architects and technical leads: I’m a big fan of the Architecture Decision Record. It increases the transparency of decision-making and makes our documentation easy to maintain, as we don’t maintain it; we just log a new decision (I wrote about it in How to successfully do documentation without a maintenance burden?). Yet, as with any tool, it’s never just. No, “just use ADRs” is not an answer. Providing a good process around that is challenging (I showed my story here). That’s why I’m happy that we’re also getting lessons-learned articles like: Pierre Pureur goes into detail on the common challenges around it. He lists three major points where ADRs should not be used for:
Great points; I fully agree; I saw that happening. I love the “Any Decision Record” term. Read the whole article; it’s worth it. Adrian Cockroft is one of the most battle-tested Engineering Managers, a person worth following. He was VP of Cloud Architecture Strategy and was one of the leading people in Netflix’s migration to a large-scale, highly available public-cloud architecture and the open-sourcing of the cloud-native NetflixOSS platform. In his InfoQ talk, he shared his retrospective on Netflix's impact on spreading the microservices and industry. It’s an intriguing talk showing various aspects like product engineering and technical and cultural bits. He concluded it with:
Speaking about transformations, GitHub proclaimed that Copilot transforms GitHub into the AI-powered developer platform. Funnily, Git was initially made as a decentralised code repository. Now, the trend is the other way round. With trunk-based development GitHub's popularity, we’re getting a fragile system that depends on a single vendor and a single pipeline. Now, this vendor will help us to write the code (also with the announced enterprise mode). I’m not against AI; I’m also using it to get a boost in coding and tedious tasks. I may sound grumpy and like a boomer, but for me, the yellow light is already blinking as it looks like a classical “first dose is for free”. We should do our due diligence and think how that will impact our development process in the long term and if this code-generation vendor locking won’t be more dangerous than cloud vendor locking. We’ll see. On a positive note, they also shared their brief description of LLM Architecture: It’s a nice and intriguing article and a must-read if you want to build your own tools around it. Getting back to the vendor lock-in AI. Of course, the companies will try to unite, as Docker, Neo4J, LangChain, and Ollama did: We'll also have some regulations like the mentioned earlier White House recommendations: But it’ll be hard to beat a big conglomerate that owns most of our common tooling. Staying in the complaining mode: what really grinds my gears is when someone blindly copies and pastes patterns and techniques from one dev environment to the other. Of course, there’s nothing wrong in adopting good patterns to the local conventions. I’m all for collaboration and learning from others. What I don’t like is when people (e.g. object-oriented developers from Java or C#) blindly bring their conventions to lightweight environments like Node.js, Go, etc. Those environments are by their nature and may not need the heavyweight ceremony. If we make them heavier, then we’re losing their competitive advantage and making the lowest common denominator. That’s why I agree with take about tooling like Nest.js: I even came up recently with a meme: Recently, in the full stack Javascript frameworks, there was also discussion about a similarly looking but much different framework: Next.js. It’s a different story, but if you’re thinking about using it (like I do), then it’s worth checking the pros and cons. Yes, frontend architecture is also architecture. Check also other links! 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
DevOpsDatabasesTestingNode.jsAI
JavaJVM.NET
TypeScriptWebAssemblyIndustry
SecurityYou're currently a free subscriber to Architecture Weekly. For the full experience, upgrade your subscription. |
Older messages
Architecture Weekly #152 - 6th November 2023
Monday, November 6, 2023
Let's look today at the Event-Driven Architecture foundations. How to start? What does it mean that they're async? What's the Clickbait Event anti-pattern? Not interested in EDA? No worries
Architecture Weekly #151 - 30th October 2023
Monday, October 30, 2023
OnPremise strikes back! Or not? Can DHH and Musk be wrong? Let's check that. Let's see also yet another Okta breach and why we learned about it from CloudFlare? Will Kafka have queues? Shall we
Webinar #14 - Mateusz Jendza: Why Verified Credentials is the Future of Digital Identity!
Friday, October 27, 2023
Watch now (104 mins) | This time, a special guest Mateusz Jendza, with the topic: Why Verified Credentials is the Future of Digital Identity! Verifiable Credentials are an intriguing topic. They are an
Architecture Weekly #150 - 16th October 2023
Monday, October 23, 2023
Wow, it's the 150th edition of Architecture Weekly! Who knew? Definitely not me! Still, let's keep it rolling. This week's topics revolve around deprecating old features and how Facebook
Architecture Weekly #149 - 16th October 2023
Thursday, October 19, 2023
Today, we had a look at how to design proper event-driven APIs and event-sourced models. We didn't only finish that, but also discussed the biggest DDoS attack on all Cloud providers and finished
You Might Also Like
Tuesday Triage #200 and giveaway
Tuesday, May 14, 2024
Your weekly crème de la crème of the Internet is here! The 200th edition featuring annual subscriptions giveaway, thoughts on nearly four years of ...
🎮 How AI Tools Are Changing Game Development — Grab a Pixel 8a Instead of Waiting for Pixel 9
Tuesday, May 14, 2024
Also: Sharing Your Google Maps Trip Progress, and More! How-To Geek Logo May 14, 2024 Did You Know In a bid to keep the ingredients secret, WD-40 was never patented. 🤖 The New GPT It's Tuesday!
Meta shuts down Workplace
Tuesday, May 14, 2024
Plus: Everything that happened at Google I/O and AWS CEO steps down View this email online in your browser By Christine Hall Tuesday, May 14, 2024 Hello, and welcome back to TechCrunch PM. The team
Flattening Lists of Lists, Python 3.13, Sets, and More
Tuesday, May 14, 2024
Flattening a List of Lists in Python #629 – MAY 14, 2024 VIEW IN BROWSER The PyCoder's Weekly Logo Flattening a List of Lists in Python In this video course, you'll learn how to flatten a list
Daily Coding Problem: Problem #1441 [Easy]
Tuesday, May 14, 2024
Daily Coding Problem Good morning! Here's your coding interview problem for today. This problem was asked by Google. UTF-8 is a character encoding that maps each symbol to one, two, three, or four
Noonification: 3 Quick Ways to Optimize RecyclerView
Tuesday, May 14, 2024
Top Tech Content sent at Noon! Get Algolia: AI Search that understands How are you, @newsletterest1? 🪐 What's happening in tech today, May 14, 2024? The HackerNoon Newsletter brings the HackerNoon
Using 97 fewer cores thanks to PGO
Tuesday, May 14, 2024
Plus an HNSW indexed vector store library, a new Go game hits the Steam store, and is 'ok' ok?. | #507 — May 14, 2024 Unsub | Web Version Together with Stytch logo Go Weekly Reclaiming CPU for
Ranked | The Top 6 Economies by Share of Global GDP (1980-2024) 📈
Tuesday, May 14, 2024
Gain a unique perspective on the world's economic order from this graphic showing percentage share of global GDP over time. View Online | Subscribe Presented by: Data that drives the
Free online event this Thursday: Getting ahead with time series data
Tuesday, May 14, 2024
Free Online Event Do you know how your competitors use time series data to get ahead? Join us on Thursday, May 16 at 10am PT/1pm ET for a free, hour-long online fireside chat called “Unleash the Full
Here's the deal
Tuesday, May 14, 2024
We wanted you to be among the first to know about our plans to relaunch the Gigantic training courses that Product Collective now powers! Here's the deal: From May 20th - May 31st, anybody that