Surviving Software Architecture

Surviving Software Architecture

Sign in Subscribe

Architecture Documentation

Architecture Documentation

A discussion about how technical documentation should be. Taking special interest in the architecture documentation.

Zero Trust Architectures

Zero Trust Architectures

Why Zero Trust architectures exists, what it is and how it can be implemented.

Write Ahead Logging

Write Ahead Logging

What's a Write Ahead Log and how to implement one.

Dual Writes

Today I want to write and discuss about the "Dual Writes" problem. It's not a new problem, and definitely not caused by the event based architectures per se, but it's pretty common to face it when teams start to use event systems. A "

From sync to async, feedback strategies.

From sync to async, feedback strategies.

Generally one of the things that are most confusing when starting to use EDA's, coming from your typical REST architecture is the operation feedback, or the responses. The REST architectural style, when used on top of HTTP has a predefined, very specific set of responses depending on the

Green software, what it is, and why it matters

software architecture

Green software, what it is, and why it matters

If you read any computer news site, or follow the trends in the industry you have recently, most likely, came across the term green computing, or green software. I first heard about these terms in the ThoughtWorks 2022 March Tech Radar, in the form of Cloud Carbon Footprint, a tool

Dead Letter Queues

event based architectures

Dead Letter Queues

In today’s post I want to talk about what happens in EBA when things go wrong. We have already learnt that our system will, basically, consume and produce messages. The consumers and producers will be coded by our team, so this means that every now and then we will

Commands and events, semantics in an EBA

event based architectures

Commands and events, semantics in an EBA

In one of my previous posts I described the basic pieces of an EBA, and well, unsurprisingly the main piece is the event itself. Events come and go into the system. They get consumed, they get produced and most likely they get transformed. The event has a meaning, and contains

Introduction to Event Based Architectures

event based architectures

Introduction to Event Based Architectures

In this post I want to introduce the architectural concept of an Event Based Architecture (EBA). An architectural pattern in software engineering is a way of designing software systems in a consistent way and with an objective in mind. The main idea is to be able to reuse known working

Polling is Hard

Polling is Hard

I've been several years working in backend and data related jobs and there are some tasks that keep popping up again, one of them is the need to "listen to that database and be notified when anything changes". This problem has different solutions depending on the