Copy
View this email in your browser

Dear Architect,

Welcome back to our third issue!

This week we have in our spotlight a great idea from O'Reilly, Neal Ford is organising a katas online event for architects where we can improve our skills working with other architects in a team and sharing our experience, a great idea in my opinion!

Then I found very rich of insights the article from InfoQ about event-driven architecture.
Recently I spent some time reading a very detailed case study from AWS explaining how they organise their automation pipelines, I'm sure you will find some useful tips to implement in your pipelines too.

As you probably have understood from the previous issues, I am quite passionate about Domain-Driven Design (DDD) and in this issue I found great the overview provided by Alberto Brandolini about the state of DDD in 2020.

Finally, I thought a pragmatic guide to implement thread modelling can be handy if you are planning to introduce this practice inside your organization.

I hope you will find them useful, enjoy the read!

IN THE SPOTLIGHT

Training

Architectural Katas

What could be better than practicing software architecture with your handpicked dream team of architects?
Participants in Architectural Katas, moderated by Neal Ford, work together virtually in small groups of their choosing to solve a challenge an actual organization is facing.
Software Architecture

From Monolith to Event-Driven

Monoliths are not always single-tiered; a distributed monolith can appear as a Microservices architecture, but behaves like a monolith. An event-driven architecture is the idea that events are the units of change
Case Study

Automating safe, hands-off deployments

Amazon didn’t start out practicing continuous delivery, and developers here used to spend hours and days managing deployments of their code to production.
Security

A Guide to Threat Modelling for Developers

This article provides clear and simple steps to help teams that want to adopt threat modelling. Threat modelling is a risk-based approach to designing secure systems
Domain-Driven Design

Domain-Driven Design in 2020

A few years have passed since the original formulation, and many things happened to the concept and the community too. This page is an opinionated attempt to describe Domain-Driven Design to a newcomer, easing the burden of browsing through history
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 😉
Twitter
Website
Copyright © 2020 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