Architecture Weekly #83 - 11th July 2022

Jul 11, 2022

Welcome to the new week!

One of the first programming books I read was “Thinking in Java” by Bruce Eckel. I wanted to become a Java developer. That didn’t work out, as the first job I found was to be a C# developer. At that time, C# was a clone of Java copied into the MS enterprisy world. Java already had a lot of practices and tooling to build a serious app. .NET was wild! Big ball of mud was the popular pattern. That was 15 years ago. Fast forward. .NET became open (well, almost), and C# evolved and changed rapidly. Java as a language stagnated, yet, recent versions brought momentum back. Still, the JVM ecosystem was always vital because of the community that came up with other popular languages like Scala, Kotlin, Groovy, etc. In recent months I made a loop, and I again started to learn how to think in Java. Firstly, because I wanted to help to make EventStoreDB client more accessible, now because I’ll be doing (the next three days) a private workshop around Event Sourcing.

Call me crazy, but I have one rule: I always outsource source codes for exercises and samples if I’m preparing a private gig. That’s what I did in the last few days!

Check what I have for you:

Self-paced kit to learn Event Sourcing on practical exercises in Java. It’s not the same experience as being in a workshop, but I tried to keep README rich. If you do exercises, you should get good foundations on how Event Sourcing (and EventStoreDB) works. I also have the C# version!
Samples of simple Event Schema versioning patterns.
Samples of how to handle uniqueness in Event Sourcing.
Distributed processes with Event Sourcing in practice.

I can bluntly say that there are not a lot of resources like that. So feel invited to try them, and once you do: share the feedback and constructive criticism!

Sounds like I was pretty busy, right? That’s not precise; I was even busier. I also wrote a blog article on the quirks around timezones. Do you believe that they won’t change? Do you think that you’re safe storing your dates as UTC? Read:

Is keeping dates in UTC really the best solution?

That’s all about me! (finally)

Yet, if you’re not tired of events, check out two great talks from last year’s Event Sourcing Live conference:

See also the newly hyped JavaScript runtime (be quick, we know how that may become obsolete within a few minutes):

bun - Incredibly fast JavaScript runtime, bundler, transpiler and package manager – all in one

Check why Linux sucks:

Bryan Lunduke - Linux Sucks 2022

And how StackOverflow is engineered:

The Hanselminutes podcast - Engineering Stack Overflow with Roberta Arcoverde

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 Red Cross, the Ukraine humanitarian organisation. You may also consider joining Tech for Ukraine initiative.

Architecture Weekly

Architecture Weekly #83 - 11th July 2022

Architecture

Distributed Systems

Databases

JavaScript

Java

Linux

.NET

Tools

Coding Life

Management

Security

Industry

Discussion about this post