View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight an article sharing the implementations of CQRS, Event Sourcing and Onion Architecture with Node.js. If you have to take one of the three I'd suggest CQRS, it could really change the way you design your software.

Microservices Up & Running is a new book from O'Reilly, I didn't have a chance to read it yet but it looks very promising, it's already on the top of my reading list.

BBC started to share more insights about their cloud migration, in this article they describe how serverless helped them to power their websites.

If you worked with Kubernetes at least once, I'm sure you asked yourself at least once how to properly provision your workload. That's the article for you!

Finally, I want to share one of the first articles about multi-cloud with virtual application networks, let's see if it's an interesting topic for the audience of this newsletter.

Enjoy the read and see you next week!

In the SPOTLIGHT

Software Architecture

Patterns for designing flexible architecture in Node.js (CQRS/ES/Onion)

The project I’m building can be described as a platform which helps authors (developers, artists, writers etc.) receive feedback early on and reach the audience for their work regardless of their popularity.
It’s an online adaptation of a scientific journal publishing and peer reviewing.

Software Architecture

Microservices: Up and Running

Microservices architectures offer faster change speeds, better scalability, and cleaner, evolvable system designs. But implementing your first microservices architecture is difficult. How do you make myriad choices, educate your team on all the technical details, and navigate the organization to a successful execution to maximize your chance of success? With this book, authors Ronnie Mitra and Irakli Nadareishvili provide step-by-step guidance for building an effective microservices architecture.

Case Study

Optimising serverless for BBC Online

The BBC makes use of many different technology providers to deliver its online services. We make use of AWS’s Lambda service to deliver the serverless functionality for Web Core. There are other platforms which provide similar functionality, such as GCP’s Cloud Functions, Azure’s Functions, and Apache’s OpenWhisk. The majority of points made can be applied to any of these platforms.

Cloud

Architecting Kubernetes clusters — how many should you have?

If you use Kubernetes as the operational platform for your applications, you are confronted with some fundamental questions about the way you use clusters:

How many clusters should you have?
How big should they be?
What should they contain?

This article gets to the bottom of this question and analyses the pros and cons of some of the options you have.

Cloud

Virtual Application Networks (VAN) for Multi-Cloud, Multi-Cluster and Cloud-Edge Interconnect

There are various reasons for deploying or replicating an application in multiple locations: geographically distributed applications for enhanced performance and availability, maintain compliance, connected vehicles, local breakouts in 5G, remote edge sites, etc. This requirement makes application-oriented multi-cloud and multi-cluster connectivity an inevitable trend of cloud computing.

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

HELP US TO IMPROVE THIS NEWSLETTER!
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!