Architecture Weekly #176 - 22nd April 2024
Welcome to the new week! Let’s try to go faster than usual through the links, not because they’re less interesting, but because I’m on Santorini island trying to get some short sightseeing time. That’s not precisely resting, as it means waking up really early and walking around. Those Greek villages are beautiful, but not extremely accessible for doing that with a 4-year-old daughter. Nevertheless, to the point! Last week, we discussed an overused but applicable pattern: in-memory bus. This time, we’ll continue with the leitmotif and talk about mocking. No, I won’t mock you; I will mock TypeScript code. Node.js in version 18th added its own native Test Runner. Why did they do it? Jest looks like abandonware even after transferring to OpenJs Foundation, issues are not getting closed, and it’s slow. Vitest is a decent new alternative, but... Native Test Runner is also young but nicely integrated directly into Node.js and maintained by the core team. It’s lightweight, thanks to Thiago Valentim Martins’ suggestion and contribution. I started using it in Emmett. So far, so good; it’s really fast (each test file spawns as a Node.js subprocess); sometimes configuring it with TypeScript adds a bit of a headache, but which tool doesn’t? In my latest article, I explained how to write a simple wrapper to make mocking and verification easier. As always, I also used it to show some TypeScript tips and tricks And nay, I don't like mocks; I think that they are overused and too often harmful. Still, it’s undeniably useful to sometimes mock the implementation of the real object or verify whether we actually called it. One way or another. Thanks to that, we can test our code or application without calling external services, doing a lot of IO operations, etc. Or ensure that dependency was called. Btw. I’m in Santorini, because I was in Athens, at Devoxx Greece, where I gave a workshop and talked at the DDD Greece meetup. I extended my stay a bit, but I promised you to get to the point. So, being on Devoxx Greece, I attended the workshop run by Giannis Papadakis about the introduction to load testing with K6. I enjoyed it, as it showed how to start and do even a few advanced stuff on load testing our backends and frontend and how to apply that to our end-to-end development process. You can also do it on your own: I think load testing is an underappreciated aspect of our process. We’re too often asking the passive-aggressive question, “…but will it scale?” without backing it up with real metrics. We should gather and verify the real needs of the business and the real load. Tools like K6 can help technically do that. If you’d like to also look at alternatives, check the article by Tim Deschryver: Check also those tools that can help you meet the defined SLO and use the cloud in a more predictable and cost-effective way: And read the article by Piotr Stapp, who checked how Azure Container Apps compare their usability against the Kubernetes services: I recently found that Adidas also has a decent engineering blog. You can check their 3 article series explaining how they deal with their container platform. The first part is here: Jumping from the DevOps world to new things in Databases. You probably already know that I’m a PostgreSQL fanboy. It’s a rock-solid database capable of many things and a true shapeshifter. Check more in Dylan Paulus article on how you can use it as a graph database: Speaking about graph databases. ISO published a standard for Graph Query Language. It’s a big deal, as for now, we have multiple languages provided by different vendors, and it was hard to transition between them. Now, there’s a chance that we’ll get some unification. Neo4J wrote a story based on their perspective. Read more: Snowflake announced the public preview of Snowflake Copilot. They called it a breakthrough; I call it a nice feature enhancing the accessibility of the tool. Still, it’s worth watching advancement in this space: What’s even more interesting to watch is the slowly changing view of responsibility in our industry. For many years, most of us have been just doing a line of business applications, but as our industry is touching more and more aspects of human life, we’ll have more and more dilemmas. Recently, nine employees were arrested for occupying Google’s offices in protest of Project Nimbus, an Israeli military contract. What’s more, 28 were fired after that. Not that it’s extremely new, as computers, almost since the beginning, have been widely used in the military, but we should be more careful and embrace that what we do may not only be for good but also may actually hurt people. It doesn’t need to be even military; the British Post Office scandal or Boeing crashes are other examples. Choose wisely. Ok, I promised to be quick, but it appeared to be a bit longer! Yet, I see some signs of sunlight and less wind, so it sounds like I better be done! 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
DevOps
Databases
AIAzureAWSJava.NET
Node.jsIndustry
SecurityTriviaYou're currently a free subscriber to Architecture Weekly. For the full experience, upgrade your subscription. |
Older messages
Architecture Weekly #175 - 15th April 2024
Monday, April 15, 2024
This time we took a history lesson. We discussed the Adele Goldberg story on how Smalltalk language impacted the way we code today. We also went through the forgotten story of Harp McGovern and her
Architecture Weekly #174 - 8th April 2024
Monday, April 8, 2024
We covered this time an XZ breach story. We provided perspectives from many angles: technical details, social engineering, and human to human. We also discussed brilliant jerks and jerks telling to
Architecture Weekly #173 - 1st April 2024
Monday, April 1, 2024
We started with big-bang info from me and then jumped quickly to debugging our thinking and applying a systemic approach. Then, we discussed what the Valkey thing is and whether it is really such a
Webinar #18 - Laïla Bougriâ: Debug your thinking
Friday, March 29, 2024
Watch now (87 mins) | Did you feel that you need to debug your mind? Did your (or your colleague's) biases impact your decision-making? How to improve it? How do you reason about the reasoning?
Architecture Weekly #172 - 25th March 2024
Monday, March 25, 2024
This time, we did an all-around journey from understanding where money comes from, so budgeting. Then we followed the money and discussed OSS sustainability issues on the example of Redis and their
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