View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight a chat with Zhamak Dehghani from ThoughtWorks talking about Data Mesh, how to break the data patterns and embrace a decentralised system for your organization.

Data streams may be challenging to implement, definitely using a managed service like AWS Kinesis may help for operationalising your infrastructure, however, learning from people who have worked for a while with the technology always helps to learn new tricks.

Nick Tune is almost a permanent mention in our newsletter thanks to his quality articles, this time he provides great arguments on how to enhance the general understanding of software architecture and business domains inside your organization.

Pulling together this weekly newsletter push me on finding new angles about software architecture, this time I found an extremely interesting article that explains how to optimise the value stream and how software architecture plays a pivotal role in doing so.

After the success of Module Federation in the frontend community, this WebPack plugin plays a new role in the microservices world in conjunction with hexagonal architecture, an interesting point of view in my opinion.

Enjoy the read and see you next week!


Data Mesh

Decentralizing Data: From Data Monolith to Data Mesh

Barry describes as “one of the most exciting paradigm shifts in how we manage data at scale.” He and Zhamak discuss why traditional data architecture models are failing and how applying product thinking principles to data management is a way to harvest the data’s full potential.
Data Streams

Mastering AWS Kinesis Data Streams

I have been working with AWS Kinesis Data Streams for several years now, dealing with over 0.5TB of streaming data per day. Rather than telling you about all the reasons why you should use Kinesis Data Streams, I’ll talk about the things you should know when working with the service. At least it would have saved me some gray hair if I knew those beforehand. So if you are still reading, let’s dive in!

Software Engineering

Nurturing Design in Your Software Engineering Culture

There are a few qualities that differentiate average from high performing software engineering organisations. I believe that attitude towards the design of code and architecture is one of them.
In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.


Value Stream Management: Process Depends on Architecture

Org charts speak only to the internal structure of organizations. They don’t express that organization’s relationship with the outside world such as customers and partners. They also don’t express the organization’s most important internal relationships: Those through which work gets done.
Case Study

Clean Microservices

Module federation offers a solution to this complexity by allowing applications to be developed and integrated like monoliths, while preserving the benefits of autonomy and loose-coupling that make microservices so attractive. Using module federation (a la Zack Jackson) and extending the ideas behind clean architecture to the components of, and relations between, microservices, we can develop federated components in ways that simplify service deployment, integration, and orchestration.

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