View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight a great example of architecting for resilience. It's probably one of the few articles I found so far talking about cell-based architecture for creating resilient platforms. Moreover, the article highlights patterns for preventing a fault of the system would impact the overall architecture

Continuing our exploration on Data Mesh, I found this case study from Netflix that present a real implementation of Data Mesh in a large organisation.

Following an article that answers many to a set of questions received during a webinar about microservices communication. I really liked the answer about commands versus events, especially because these are questions we face every day when we are developing a distributed system.

Last week we highlighted a video on the connection between software architecture and organization. I found another article that highlights this concept once again.

A couple of weeks ago I discovered what monotonicity means in distributed systems in particular for scaling databases. The article introduces the CALM theorem (Consistency as Logical Monotonicity). I found it interesting because we don't often realise how much simpler our lives would be with eventual consistency in distributed systems. Food for thoughts.

Enjoy the read and see you next week!


Software Architecture

Towards continuous resilience

Let me ask you couple questions:

Do you remember your first outage?

How smart and confident did you feel back then?

I clearly remember mine. I was very nervous and sweating a lot.
I started making mistakes I usually wouldn’t. It was a disaster.
I had no idea what I was doing.
Data Mesh

Netflix Data Mesh

Netflix processes trillions of events and petabytes of data a day in the Keystone data pipeline, which is built on top of Apache Flink. As Netflix has scaled up original productions annually enjoyed by more than 150 million global members, data integration across the streaming service and the studio has become a priority.


Communication Between Loosely Coupled Microservices

In the recent webinar titled “Communication Between Loosely Coupled Microservices” we got a lot of great questions and because of the limited time some were left unanswered. As community questions are really important to me I want to follow my tradition to answer remaining questions in a blog post

Software Architecture

What is an Organic (Microservice) Architecture?

The best architectural style to support an agile enterprise is that of an organic architecture. An organic architecture is a service landscape that consists of digital business capabilities and evolves through organic federated growth.
Distributed Systems

Keeping CALM: when distributed consistency is easy

When it comes to high performing scalable distributed systems, coordination is a killer. It’s the dominant term in the Universal Scalability Law. When we can avoid or reduce the need for coordination things tend to get simpler and faster. See for example Coordination avoidance in database systems, and more recently the amazing performance of Anna which gives a two-orders-of-magnitude speed-up through coordination elimination. So we should avoid coordination whenever we can.

Thanks for reading Dear Architects 🙏

If you have any suggestions to make this newsletter better, just drop us an email!

Have a great rest of the week 😉

Opinions are my own

We just need a few minutes of your time to make Dear Architects even better
Sure! Let me share what I think about Dear Architects!
Copyright © 2021 deararchitects, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp