Dec 12

Welcome to the new week!

In case you missed it, don’t forget to check the webinar recording with Alexey Zimarev, made exclusively for our community.

Alexey explained his motivation for building his Eventuous framework sharing his insights and experience around Event Sourcing and Event-Driven Architecture.

I'm also thrilled to announce that I'll be responsible with the Domain-Driven Design Europe team for curating the next EventSourcingLive conference lineup!

We want to prove that Event Sourcing s a highly practical pattern and show its real-world usage. We want to learn about both big successes adopting it and horror stories. Your stories. Don’t hesitate to send your proposal and contact me if you have any questions. I’m here to help. Read more in:

Share your story on Event Sourcing Live 2023

While learning the technology and patterns, it’s worth considering not only 0-day issues but also the 2nd and 3rd-day cases that may come later. Still, it’s harder to do than it may seem. I saw many times were people were so focused on the potential future that they were not delivering the features to get them through the first day. We need to note the risks and have a plan to expand, but we should at first focus on the stuff we got to do now. Understand the scenario, and then pick our poison. In this sense, check the great talks about stuff that can go wrong, but we can live with that if we’re prepared:

Yet, a decent plan is not enough. The proper execution needs to go with it. Disregarding the importance of the technical details may also cost us a big failure. An example of that can be those case studies about Elastic Search:

They’re also good examples of the materials we should learn from. It’s not enough to know that something may fail. We won’t learn much from other people’s mistakes if those studies are not success stories of how they recovered. Knowing that something may fail without knowing how to fix it will just cause headaches and scare us.

Looking at such security research made by Bleeping Computers can be indeed scary. Knowing how many Docker images are full of vulnerabilities can lead to Fox Mulder's maxim: “Trust no one”.

Bleeping Computer - Docker Hub repositories hide over 1,650 malicious containers

Artificial Intelligence is getting more and more intriguing use cases. I’m not even sure how to comment on this one:

TechCrunch - Meet Unstable Diffusion, the group trying to monetize AI porn generators

Amazon delivered CodeCatalyst, the response for GitHub Codespaces. It’s intriguing how we’re circling in our industry. When I started, it was popular to work on the preconfigured Virtual Machines, as getting the proper onboarding and dev environment configuration from zero could last from days to even weeks. Are we going back?

Amazon CodeCatalyst - Dev Environments

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.