View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight a great interview to Adrian Cockcroft who is sharing is predictions for the future of cloud and software architecture. I don't want to spoil anything, but you have to know that is an epic episode!

Microservices Patterns is not a new book, however it gathers a great collection of design patterns with a clear explanation and code examples written in Java.

Have you ever had challenges handling retries? Dealing with microservices it may be hard sometimes but we can learn from each other. In this post we are going to learn more about retries with RabbitMQ, but don't think some of these techniques are applicable only there.

Last February I attended my last in-person conference, one of the session was a case study on how Conde Nast introduced GraphQL in their organisation, interesting especially for everyone trying to embark in a similar journey

Finally, the third and last article of this mini-series from Nick Tune regarding team topologies and domain-driven design. If you have read the first 2, this is a perfect conclusion.

Enjoy the read and see you next week!


Software Architecture

Episode 15: Adrian Cockcroft

In this episode, Mik and Adrian provide concrete advice on moving ahead in the digital world, and cover many key discussion points including:

- Insight into Adrian’s experiences establishing technical practices in organizations like eBay, Netflix and AWS.
- The importance of product-centred innovation in order to pave the path for faster success.
- Business agility, and why all organizations must have this in order to innovate and stay ahead of the competition.
- The importance of feedback loops when delivering software, with a key focus on the four stages of the OODA loop.
- The notion of ‘Flow Time’ or ‘Time to Value’ and why it is a crucial and powerful metric that all CEO’s must prioritize.
- The use of VSM in order to achieve better decision making and build a scalable organization.
Software Architecture

Microservices Patterns

Microservices Patterns teaches enterprise developers and architects how to build applications with the microservice architecture. Rather than simply advocating for the use the microservice architecture, this clearly-written guide takes a balanced, pragmatic approach, exploring both the benefits and drawbacks.

Case Study

A tale of retries using RabbitMQ

Firstly, who should be responsible for the retry logic? In our architecture we actually introduced two types of communication models between Microservices. The first one is a request-response model, which we implemented using promises (completable futures) on top of RabbitMQ. The second one is a broadcast or publish-subscribe model, where Microservices are more decoupled from each other, as events are published on the message broker (RabbitMQ in this case) and interested parties subscribe for these events to execute their business logic.

Case Study

Introducing and Scaling a GraphQL BFF

During QCon London 2020 I attended this session from Michelle who was working in Conde Nast at the time.
She provides their journey on embracing GraphQL at scale in their fashion portals, all the challenges and solutions found for applying GraphQL in their context.

Team Topologies and DDD

Architecture Ownership Patterns for Team Topologies. Part 3: Multi-Team Patterns

As a system grows, higher-order abstractions are needed for ease of understanding, communication, and management. In Geography, continents are a higher order abstraction that allow us to collectively describe a large number of countries in a single word. As businesses grow, higher order abstractions are needed to organize groups of teams working on related challenges, like products or domains.
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