Copy
View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight the tool I'd love having several years ago for maintaining architecture diagrams up to date and understanding in the blink of an eye new architectures deployed on AWS.

For this issue I thought to recommend another bestseller from the well-known Rob C. Martin or Uncle Bob.
Clean Architecture is an opinionated book that explains what software architects need to achieve and core disciplines and practices for achieving it.

Following two case studies, the first one on one of the largest real-time streaming systems in the world and the second one on the decision made by InVision to move back to a monolithic architecture.

Finally an article that describes a very useful microservices pattern like bulkhead pattern for improving he resilience of the services.

Enjoy the read and see you next week!

In the SPOTLIGHT

Tools

AWS Perspective


AWS Perspective is a tool that quickly visualizes AWS Cloud workloads as architecture diagrams. You can use the solution to build, customize, and share detailed workload visualizations based on live data from AWS. This solution works by maintaining an inventory of the AWS resources across your accounts and Regions, mapping relationships between them, and displaying them in a web user interface

Github project
Software Architecture

Clean Architecture

As with his other books, Martin's Clean Architecture doesn't merely present multiple choices and options, and say "use your best judgment": it tells you what choices to make, and why those choices are critical to your success.
Clean Architecture is essential reading for every software architect, systems analyst, system designer, and software manager

Case Study

We Built The World's Largest Real time High-Frequency, Low Latency Streaming System on Golang

We run one of the largest real-time, high-frequency, low-latency streaming systems in the world with over 3 million messages per second and over 1320 billion messages per month. We call these Quotes Streamers.

Case Study

Why I've Been Merging Microservices Back Into The Monolith At InVision

I wanted to start this post off by stating unequivocally that I am not anti-microservices. My merging of services back into the monolith is not some crusade to get microservices out of my life. This quest is intended to "right size" the monolith. What I am doing is solving a pain-point for my team.
Design Patterns

Maintaining Resilience in a Microservice Architecture

One of the most important aspects of a microservice architecture is resiliency. The available resources of a client that consumes a remote service should never be exhausted if the service is failing, but instead, they should be released fast for further use. Netflix’s Hystrix, a battle-tested library which implements common resiliency patterns like circuit breaker and bulkhead, comes to our aid for designing a highly resilient microservice architecture.
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 😉

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!
Twitter
Website
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