View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we celebrate "software at scale" with a couple of case studies. The first one from Uber engineering with a series of posts on how they have re-architected the fulfilment platform from the ground up. Then we discover how Wix is using micro-frontends for scaling their complex platform on the frontend side.

I found very pleasant this podcast between three well-known names in the microservices community. The considerations shared on how microservices evolved are very insightful and often we don't realise that the technical side is just a small part of this architecture.

I searched for a while for a good article about tips and tricks on designing great architecture diagrams, I'm eager to know what you think about this one.

Finally, HTTP/3 is knocking on our door, are we ready to know more about this new protocol and how we can fully leverage its new features?

Enjoy the read and see you next week!


Case Study

Ground-up Re-architecture to Accelerate Uber’s Go/Get Strategy

Two years ago, we made a bold bet and embarked on a journey to rewrite the Fulfillment Platform from the ground up, as the architecture built in 2014 would not scale for the next decade of Uber’s growth. 


What Have We Learned over the Last Decade of Microservices?

If your organization delivers software too slowly, adopting microservices will not fix that, and could make it worse. You first need to raise the maturity level for delivering software, making code easier to deploy and maintain; at which point, you may not even need microservices.

Software Architecture

Better Architecture Diagrams for Agile Teams: actionable tips and lessons.

Architecture diagrams are like text documents. It’s easy to create one. But it’s hard to create a good one. I would argue that for technical documentation, diagrams are even more difficult.


Taking micro-frontends to the next level

In this article I’d like to share some of the things we did in order to evolve the concept of developing big scale micro-frontends (at the time of writing this article we have 700 developers working on this architecture).


HTTP/3 From A To Z: Core Concepts (Part 1)

In this article series, I will discuss the new protocol, especially its performance features, with more nuance. I will show that, while HTTP/3 indeed has some promising new concepts, sadly, their impact will likely be relatively limited for most web pages and users (yet potentially crucial for a small subset). HTTP/3 is also quite challenging to set up and use (correctly), so take care when configuring the new protocol.

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