In which Alex explains the meaning of this phrase: “The threat actor used OSINT reconnaissance to map our attack surface, exploited a vulnerability to gain initial access, then used lateral movement and privilege escalation before exfiltrating PII and establishing persistence”| Mozaic Works
Residuality theory is a fascinating theory about designing stable architecture over time, created by Barry O’Reilly. Alex takes a look at it, and it might be the practice that solves software architecture and design. Links:| mozaicworks.com
InfoQ has published the latest AI, ML and Data Engineering Report for 2025, and Alex reacts to the parts that affect software development.| Mozaic Works
Can Claude help with infrastructure automation? Alex took it for a spin, and these are his conclusions: an experience report on using Claude to learn and solve infrastructure automation problems. A few brief ideas: Learn more from the video!| Mozaic Works
The InfoQ Software Architecture and Design Trends for 2025 provides interesting insights about the state of software architecture, so let's take a look. One interesting take away is AsyncAPI.| Mozaic Works
Doing the simplest thing that could possibly work often involves incremental thinking: the engineering practice of splitting a large problems into smaller problems so that their resolution grows into the solution that you are looking for. Let's see a definition and a few examples.| Mozaic Works
In software architecture and design, your best bet is to do the simplest thing that could possibly work to solve the problem you know now rather than reach the ideal state of the system. Yet, this is not the default way of designing software. So how can we do better? Let’s see, with the help […]| Mozaic Works
We've often noticed how people starting with a technique imbue it with a lot of potential to solve all the problems of software development (* exaggerating for effect). This is rarely the case. Let's look in particular at domain modeling, and how bounded contexts are not 1-to-1 to business domains, inspired by another excellent article written by Mattias Verraes.| Mozaic Works
LLMs have many ethical implications, and we decided to tackle them head on in this video, in the context of using AI assistants to generate code and other software development artifacts. The brief:The top issues for using LLMs for software development are: copying the whole internet to build the models, possible copyright infringement in generated […]| Mozaic Works
What to do when you can’t ensure that services will run normally and return correct data? We have our Sagas and our Circuit Breakers, but maybe there’s a cleaner way. Let’s have a look at the Scheduler – Agent – Supervisor architectural pattern. Links:| Mozaic Works
A recent LinkedIn post makes the point that before moving to microservices you should ask what is the bottleneck. Let’s look in more detail. Links:| Mozaic Works
Overengineering is a common problem in software development. Does hexagonal architecture fit this pattern? Let’s examine this idea. Links:| mozaicworks.com
Software architecture is about trade-offs, but what does this mean and how do we deal with them? Links:| mozaicworks.com
